Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
torch.io scored 92/100, demonstrating a strong security posture. Minor improvements are noted below.
Positive signals: TLS Configuration, DMARC / Email Security, Known Breaches all passed.
2 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 torch.io compares
Grade distribution across 2599 companies we've scanned. torch.io scores better than 92% of them.
84
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
torch.io — Grade A- (92/100)
2599 companies scanned
Security checks
Each check inspects a different part of torch.io's public security setup. Green means healthy, yellow needs attention, red is a problem.
DNS Configuration
Strengths: 4 nameservers configured (ns-35.awsdns-04.com., ns-939.awsdns-53.net., ns-1425.awsdns-50.org., ns-1846.awsdns-38.co.uk.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
HSTS Header
HSTS present but max-age is low (2592000s). Recommended minimum: 15768000 (6 months).
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DMARC / Email Security
Strengths: DMARC policy set to reject (strongest); SPF record present with soft-fail (~all); DKIM configured (selectors: google, s1, s2, smtpapi).
Known Breaches
No known breaches found in public disclosure databases.
Security Headers
4/5 security headers present. Missing: CSP.
CVE Exposure
Detected technologies: cloudflare, WP Engine. (cloudflare 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, 59 days remaining; Issued by Google Trust Services.
Recommended actions
2 items
Steps to improve torch.io's security grade, ranked by impact.
1
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for torch.io 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 .io TLD
4
Verify: dig +dnssec torch.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
Increase HSTS max-age duration
HSTS is enabled but the max-age (0s) is below the recommended minimum of 15768000s (6 months). A short max-age means browsers forget the HTTPS-only policy quickly, reducing protection between visits.
Compliance impact
PCI-DSS 4.0Req 6.4.1
Application security header configuration
How to fix this
1
Update header: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
2
Verify: curl -sI https://torch.io | grep -i strict
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 soft-fail (~all); DKIM configured (selectors: google, s1, s2, smtpapi).
SPF Record
Present
v=spf1 include:_spf.google.com ip4:199.15.214.31 include:_spf.atlassian.net include:_spf.salesforce.
Security Headers
4/5 present
Missing: CSP
HSTS
Not enabled
HSTS present but max-age is low (2592000s). Recommended minimum: 15768000 (6 months).
SSL Certificate
Valid
Strengths: Certificate valid, 59 days remaining; Issued by Google Trust Services.
DNSSEC
Not enabled
Strengths: 4 nameservers configured (ns-35.awsdns-04.com., ns-939.awsdns-53.net., ns-1425.awsdns-50.org., ns-1846.awsdns-38.co.uk.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.