Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
mod.io scored 95/100, demonstrating a strong security posture. Minor improvements are noted below.
Positive signals: MX Records & Mail Provider, TLS Configuration, DNS Configuration all passed.
1 action item 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 mod.io compares
Grade distribution across 2497 companies we've scanned. mod.io scores better than 96% of them.
78
A+
25
A
183
A-
190
B+
72
B
347
B-
120
C+
116
C
319
C-
116
D+
94
D
237
D-
600
F
mod.io — Grade A (95/100)
2497 companies scanned
Security checks
Each check inspects a different part of mod.io's public security setup. Green means healthy, yellow needs attention, red is a problem.
MTA-STS & TLS Reporting
Issues: No MTA-STS configured — email in transit is vulnerable to TLS downgrade attacks. Sending servers cannot verify that your mail server requires TLS; No TLSRPT record — TLS delivery failures won't be reported to domain owner.
DNS CAA Records
No CAA records found. Without CAA, any Certificate Authority can issue certificates for this domain. Adding CAA records restricts issuance to authorized CAs only, reducing the risk of misissued certificates.
Security Headers
3/5 security headers present. Missing: X-Frame-Options, Permissions-Policy.
Cookie Security
Strengths: 1 cookie(s) analyzed; All cookies have Secure flag; All cookies have HttpOnly flag. Issues: 1/1 cookie(s) missing SameSite attribute (__cf_bm).
MX Records & Mail Provider
Strengths: Mail handled by Google Workspace; 5 MX record(s) configured; Multiple MX records provide redundancy.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DNS Configuration
Strengths: 2 nameservers configured (johnny.ns.cloudflare.com., dorthy.ns.cloudflare.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.
TLS Protocol Support
Strengths: TLS 1.3 supported; TLS 1.2 supported; TLS 1.3 supported (strongest). Protocol support: TLS 1.3: Yes, TLS 1.2: Yes, TLS 1.1: No, TLS 1.0: No.
HSTS Header
HSTS enabled: max-age=31536000s (365 days) with includeSubDomains and preload. Meets best-practice configuration.
Known Breaches
No known breaches found in public disclosure databases.
DMARC / Email Security
Strengths: DMARC policy set to reject (strongest); SPF record present with hard-fail (-all); DKIM configured (selectors: google, k1).
security.txt (RFC 9116)
Strengths: security.txt found with 4 field(s); Contact: mailto:[email protected]; Encryption key provided for secure reporting; Disclosure policy: ; Security hiring link included. Issues: Missing 'Expires' field (required by RFC 9116); Not PGP signed (recommended for authenticity).
CVE Exposure
Detected technologies: cloudflare. (cloudflare detected but excluded from CVE matching — upstream infrastructure). All detected technologies are upstream CDN/proxy infrastructure. No application-level software versions exposed.
Certificate Hygiene
Strengths: Certificate valid, 41 days remaining; Issued by Google Trust Services.
Recommended actions
1 item
Steps to improve mod.io's security grade, ranked by impact.
1
Add optional security headers (X-Frame-Options, Permissions-Policy)
mod.io has most security headers configured. Missing: X-Frame-Options, Permissions-Policy. These are best-practice additions that reduce the attack surface for client-side vulnerabilities.
How to fix this
1
Add: X-Frame-Options: SAMEORIGIN (use DENY only if you never embed your pages in iframes)
2
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
3
Verify with: curl -sI https://mod.io | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
At a glance
Key data points from the 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=reject
Strengths: DMARC policy set to reject (strongest); SPF record present with hard-fail (-all); DKIM configured (selectors: google, k1).
SPF Record
Present
v=spf1 include:_spf.google.com include:amazonses.com -all
Security Headers
3/5 present
Missing: X-Frame-Options, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=31536000s (365 days) with includeSubDomains and preload. Meets best-practice configuration.
SSL Certificate
Valid
Strengths: Certificate valid, 41 days remaining; Issued by Google Trust Services.
DNSSEC
Enabled
Strengths: 2 nameservers configured (johnny.ns.cloudflare.com., dorthy.ns.cloudflare.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.