Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
index.io scored 82/100, demonstrating a strong security posture. Minor improvements are noted below.
Positive signals: Known Breaches, TLS Configuration, DNS Configuration all passed.
3 action items identified, including 0 critical. The issues are configuration gaps, not architectural problems. A focused remediation effort of 2–5 days could address all findings.
How index.io compares
Grade distribution across 2598 companies we've scanned. index.io scores better than 72% of them.
83
A+
25
A
190
A-
196
B+
75
B
362
B-
129
C+
114
C
330
C-
119
D+
95
D
252
D-
628
F
index.io — Grade B- (82/100)
2598 companies scanned
Security checks
Each check inspects a different part of index.io's public security setup. Green means healthy, yellow needs attention, red is a problem.
DMARC / Email Security
Strengths: SPF record present with soft-fail (~all); DKIM configured (selectors: google). Issues: DMARC policy is 'none' (monitoring only, no enforcement).
Security Headers
3/5 security headers present. Missing: CSP, Permissions-Policy.
Certificate Hygiene
Strengths: Certificate valid, 152 days remaining; Issued by Amazon. Issues: Wildcard certificate in use — broader attack surface if compromised.
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.
DNS Configuration
Strengths: 4 nameservers configured (ns-567.awsdns-06.net., ns-1142.awsdns-14.org., ns-1582.awsdns-05.co.uk., ns-428.awsdns-53.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.
HSTS Header
HSTS enabled: max-age=31536000 with includeSubDomains and preload. Meets best-practice configuration.
CVE Exposure
Detected technologies: AmazonS3, Proxy/CDN. (Proxy/CDN detected but excluded from CVE matching — upstream infrastructure). No version information exposed — CVE matching not possible (this is good practice).
Recommended actions
3 items
Steps to improve index.io's security grade, ranked by impact.
1
Strengthen email authentication configuration
Email authentication is partially configured for index.io but has gaps. Actions needed: upgrade DMARC policy from 'none' to 'quarantine' or 'reject'. Until DMARC enforcement is active, spoofed emails may still reach recipients.
Compliance impact
NIST CSFPR.AC-7
Email authentication is a required access control
How to fix this
1
Upgrade DMARC policy to p=quarantine (then p=reject after monitoring)
2
Verify with: nslookup -type=txt _dmarc.index.io
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 optional security headers (CSP, Permissions-Policy)
index.io has most security headers configured. Missing: CSP, Permissions-Policy. These are best-practice additions that reduce the attack surface for client-side vulnerabilities.
How to fix this
1
Add Content-Security-Policy header (start with report-only to avoid breakage)
2
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
3
Verify with: curl -sI https://index.io | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
3
Review certificate configuration
Certificate issues found for index.io: wildcard certificate in use. Wildcard certificates have a broader blast radius if compromised. These are operational hygiene items, not immediate security risks.
How to fix this
1
Consider replacing wildcard cert with individual certs for critical subdomains
2
Consolidate certificate issuance to 1–2 trusted CAs
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
p=none
Strengths: SPF record present with soft-fail (~all); DKIM configured (selectors: google). Issues: DMARC policy is 'none' (monitoring only, no enforcement).
SPF Record
Present
v=spf1 include:_spf.google.com include:amazonses.com ~all
Security Headers
3/5 present
Missing: CSP, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=31536000 with includeSubDomains and preload. Meets best-practice configuration.
SSL Certificate
Issues
Strengths: Certificate valid, 152 days remaining; Issued by Amazon. Issues: Wildcard certificate in use — broader attack surface if compromised.
DNSSEC
Enabled
Strengths: 4 nameservers configured (ns-567.awsdns-06.net., ns-1142.awsdns-14.org., ns-1582.awsdns-05.co.uk., ns-428.awsdns-53.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.