Is globe.exchange safe to use as a vendor?

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

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; SPF record present with soft-fail (~all); DKIM configured (selectors: google).

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.

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

Q: 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.

Q: Does globe.exchange use HSTS?

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

Q: Is globe.exchange's SSL certificate valid?

Issues detected. Strengths: Certificate valid, 50 days remaining; Issued by Google Trust Services. Issues: Wildcard certificate in use — broader attack surface if compromised.

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- 92/100

globe.exchange

February 18, 2026 ·

1+ Warnings 6 Passed

Better than 92% of 2692 companies scanned.

092th pct100

A+

A-

B+

B-

C+

C-

D+

D-

A-

globe.exchange

92/100

Enable DNSSEC on your domain

1–3 days (depends on registrar)

Without DNSSEC, DNS responses for globe.exchange can be spoofed, potentially redirecting users to malicious sites. This requires coordination with your domain registrar to publish DS records.

NIST 800-53SC-20

Secure name/address resolution service

How to fix this

1Check if your DNS provider supports DNSSEC (Cloudflare, Route53, etc.)

2Enable DNSSEC signing in your DNS provider dashboard

3Add the DS record to your registrar for .exchange TLD

4Verify: dig +dnssec globe.exchange

At a glance

Full data from this scan

TLS Version

TLSv1.3

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

DMARC Policy

p=quarantine

Strengths: DMARC policy set to quarantine; SPF record present with soft-fail (~all); DKIM configured (selectors: google).

SPF Record

Present

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

Security Headers

4/5 present

Missing: Permissions-Policy

HSTS

Enabled

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

SSL Certificate

Issues

Strengths: Certificate valid, 50 days remaining; Issued by Google Trust Services. Issues: Wildcard certificate in use — broader attack surface if compromised.

DNSSEC

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.

Similar companies