Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
earth-ai.com scored 72/100, meeting baseline requirements but with 1 finding that require attention. The vendor can proceed with a remediation timeline agreement.
Critical gaps in: Security Headers, DMARC / Email Security. Positive signals: Known Breaches, TLS Configuration, HSTS Header all passed.
3 action items identified, including 1 critical. The issues are configuration gaps, not architectural problems. A focused remediation effort of 2–5 days could address all findings.
How earth-ai.com compares
Grade distribution across 2378 companies we've scanned. earth-ai.com scores better than 47% of them.
71
A+
22
A
180
A-
181
B+
69
B
333
B-
111
C+
111
C
295
C-
110
D+
92
D
216
D-
587
F
earth-ai.com — Grade C- (72/100)
2378 companies scanned
Security checks
Each check inspects a different part of earth-ai.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
Security Headers
Only 1/5 security headers present. Missing: CSP, X-Frame-Options, Referrer-Policy, Permissions-Policy. This exposes the application to clickjacking, MIME-sniffing, and other client-side attacks.
DMARC / Email Security
Issues: No DMARC record found — email spoofing is not prevented; No SPF record found; No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
DNS Configuration
Strengths: 2 nameservers configured (ns69.domaincontrol.com., ns70.domaincontrol.com.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
Known Breaches
No known breaches found in public disclosure databases.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
HSTS Header
HSTS enabled: max-age=31536000. Missing includeSubDomains. Missing preload directive.
CVE Exposure
Detected technologies: Netlify, Next.js. (Netlify detected but excluded from CVE matching — upstream infrastructure). No version information exposed — CVE matching not possible (this is good practice).
Certificate Hygiene
Strengths: Certificate valid, 48 days remaining; Issued by Let's Encrypt.
Recommended actions
3 items
Steps to improve earth-ai.com's security grade, ranked by impact.
1
Set up email authentication (DMARC, SPF, DKIM)
Without email authentication, anyone can send emails that appear to come from earth-ai.com. This is the most common vector for phishing attacks targeting employees and customers. DMARC, SPF, DKIM are not configured.
Compliance impact
NIST CSFPR.AC-7
Email authentication is a required access control
ISO 27001A.13.2.1
Information transfer policies require email security controls
HIPAA§164.312(e)
Transmission security for electronic PHI
How to fix this
1
Add SPF record to DNS: v=spf1 include:_spf.google.com ~all (adjust for your email provider)
2
Configure DKIM signing with your email provider and publish the public key in DNS
3
Add DMARC record: v=DMARC1; p=quarantine; rua=mailto:[email protected]
4
Monitor DMARC reports for 2–4 weeks, then upgrade policy to p=reject
See all recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
2
Add missing security headers (CSP, X-Frame-Options, Referrer-Policy, Permissions-Policy)
4 of 5 recommended security headers are missing on earth-ai.com: CSP, X-Frame-Options, Referrer-Policy, Permissions-Policy. These headers protect against clickjacking, MIME-sniffing, and unauthorized browser feature access. Adding them is a server configuration change with no application code changes required.
Compliance impact
PCI-DSS 4.0Req 6.4.1
Security headers are required application controls
OWASPSecure Headers
Recommended baseline for web applications
How to fix this
1
Add Content-Security-Policy header (start with report-only to avoid breakage)
2
Add: X-Frame-Options: DENY (or SAMEORIGIN if you use iframes)
3
Add: Referrer-Policy: strict-origin-when-cross-origin
4
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
5
Verify with: curl -sI https://earth-ai.com | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
3
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for earth-ai.com can be spoofed, potentially redirecting users to malicious sites. This requires coordination with your domain registrar to publish DS records.
Compliance impact
NIST 800-53SC-20
Secure name/address resolution service
How to fix this
1
Check if your DNS provider supports DNSSEC (Cloudflare, Route53, etc.)
2
Enable DNSSEC signing in your DNS provider dashboard
3
Add the DS record to your registrar for .com TLD
4
Verify: dig +dnssec earth-ai.com
At a glance
Key data points from the scan.
TLS Version
TLSv1.3
TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DMARC Policy
Not configured
Issues: No DMARC record found — email spoofing is not prevented; No SPF record found; No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
SPF Record
Missing
No SPF record found.
Security Headers
1/5 present
Missing: CSP, X-Frame-Options, Referrer-Policy, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=31536000. Missing includeSubDomains. Missing preload directive.
SSL Certificate
Valid
Strengths: Certificate valid, 48 days remaining; Issued by Let's Encrypt.
DNSSEC
Not enabled
Strengths: 2 nameservers configured (ns69.domaincontrol.com., ns70.domaincontrol.com.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.