Is globe.exchange safe to use as a vendor?

globe.exchange scored 90/100 on LynxRadar's security posture assessment. The domain meets baseline security requirements. 8 checks passed, 2 warnings, 0 critical issues across 10 passive checks including TLS, DMARC, security headers, breaches, and CVEs.

What TLS version does globe.exchange use?

globe.exchange uses TLSv1.3 with TLS_AES_256_GCM_SHA384. TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.

Does globe.exchange have SPF configured?

Yes. SPF record: v=spf1 include:amazonses.com include:_spf.google.com ~all

Does globe.exchange have security headers configured?

globe.exchange has 4 of 5 recommended security headers. Present: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy. Missing: Permissions-Policy.

Does globe.exchange use HSTS?

Yes. HSTS enabled: max-age=31536000 with includeSubDomains and preload. Meets best-practice configuration.

Has globe.exchange been involved in a data breach?

No known breaches found. No known breaches found in public disclosure databases.

Does globe.exchange have known CVE vulnerabilities?

Detected technologies: cloudflare, Next.js. (cloudflare detected but excluded from CVE matching — upstream infrastructure). No version information exposed — CVE matching not possible (this is good practice).

Is globe.exchange's SSL certificate valid?

Yes. Strengths: Certificate valid, 50 days remaining; Issued by Google Trust Services. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.

globe.exchange Security Report — Grade A- (90/100)

Q: Does globe.exchange have DMARC configured?

Yes. globe.exchange's DMARC policy is set to 'quarantine'. SPF record: yes. Strengths: DMARC policy set to quarantine; DMARC pct=100 — policy applies to all mail; DMARC sp=reject — subdomains fully protected; Aggregate reports (rua) configured; Forensic reports (ruf) configured; SPF soft-fail (~all) configured; SPF DNS lookup count: 2/10 (within limit); DKIM configured (selectors: google). Issues: DMARC policy is 'quarantine', not 'reject' — spoofed mail is moved to spam rather than blocked outright.

Q: Does globe.exchange have DNSSEC enabled?

No. Strengths: 2 nameservers configured (decker.ns.cloudflare.com., eloise.ns.cloudflare.com.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.

A-

Trust rating

Excellent · 90/100

Procurement snapshot

No critical findings. The 2 remaining items are configuration gaps, not architectural problems.

Strengths

Known Breaches

TLS Configuration

MX Records & Mail Provider

HSTS Header

Questions to ask

Confirm DNSSEC rollout timeline

Estimated remediation effort: 1–4 days

Based on a passive external scan — supplement with vendor-provided attestations, not a replacement.

Trust Score Trend

→ No change 1 scan · Last scanned February 18, 2026

Your rating Industry average

Score

100 75 50 25 0

A-

globe.exchange

90/100

Compliance & Certifications

Not yet verified

SOC 2 Type II

Audit report not on file

3rd party · AICPA

ISO 27001

Certificate not on file

3rd party · accredited body

GDPR

DPA not on file

Self-reported

Incident History

No public breaches on record

Security Posture

2 items need attention

8 passed

Finish setting up email authentication

DMARC / Email Security

2–4 hours High

Spoofed emails can still reach your customers and partners until this is fully enforced. Email authentication for globe.exchange is partly set up, but there are gaps: your DMARC policy is "quarantine", so spoofed mail lands in spam instead of being blocked. Until it's fully in place, someone could still send a convincing fake email pretending to be you.

NIST SP 800-177r1§4

Trustworthy Email recommends SPF, DKIM and DMARC for every email domain

How to fix this

1Once your DMARC reports show no legitimate mail failing, change the policy from "quarantine" to "reject" in your DNS settings (you're using Google Workspace — see https://knowledge.workspace.google.com/admin/security/set-up-dkim) so spoofed mail is blocked outright. Your current record with just that change:

v=DMARC1; p=reject; sp=reject; rua=mailto:[email protected]; ruf=mailto:[email protected]

2Double-check it's live: search "dmarc record checker" and enter globe.exchange.

Email authentication guide

Report unlocked.

View all 8 passed checks

Known Breaches

TLS Configuration

MX Records & Mail Provider

HSTS Header

Security Headers

CVE Exposure

Certificate Hygiene

Subprocessors & Tech Stack

Company Signals

Operational risk

Last funding

Employees

Trust Resources

Claim profile →

Trust Center

Not detected

DPA (Data Processing Agreement)

Subprocessors List

Tech Stack Detected

Subprocessors

Cloudflare

Similar companies in B2B SaaS / Software

Appears in

B2B SaaS / Software vendors

770 companies scanned by LynxRadar

Vendors graded A

390 companies · LynxRadar ranking

High Priority

p=quarantine

Strengths: DMARC policy set to quarantine; DMARC pct=100 — policy applies to all mail; DMARC sp=reject — subdomains fully protected; Aggregate reports (rua) configured; Forensic reports (ruf) configured; SPF soft-fail (~all) configured; SPF DNS lookup count: 2/10 (within limit); DKIM configured (selectors: google). Issues: DMARC policy is 'quarantine', not 'reject' — spoofed mail is moved to spam rather than blocked outright.

Likelihood: ★★★☆☆

Impact: ★★★☆☆

Medium Priority

Not enabled

Strengths: 2 nameservers configured (decker.ns.cloudflare.com., eloise.ns.cloudflare.com.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.

Likelihood: ★★☆☆☆

Impact: ★★★☆☆