Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
terraform.io scored 70/100, meeting baseline requirements but with 2 findings that require attention. The vendor can proceed with a remediation timeline agreement.
Positive signals: Known Breaches, TLS Configuration, CVE Exposure 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 terraform.io compares
Grade distribution across 2599 companies we've scanned. terraform.io scores better than 42% 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
terraform.io — Grade C- (70/100)
2599 companies scanned
Security checks
Each check inspects a different part of terraform.io's public security setup. Green means healthy, yellow needs attention, red is a problem.
DMARC / Email Security
Strengths: DMARC policy set to reject (strongest). Issues: DMARC has no aggregate report URI (rua); No SPF record found; No DKIM records found for common selectors (may use non-standard selectors).
DNS Configuration
Strengths: 4 nameservers configured (ns-1228.awsdns-25.org., ns-1672.awsdns-17.co.uk., ns-297.awsdns-37.com., ns-702.awsdns-23.net.); Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
HSTS Header
Could not fetch https://terraform.io — connection failed or timed out.
Security Headers
Could not fetch https://terraform.io — connection failed or timed out.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
Known Breaches
No known breaches found in public disclosure databases.
CVE Exposure
No server software versions detected in HTTP response headers. This is good practice (version hiding) but means CVE exposure cannot be assessed from external signals alone.
Certificate Hygiene
Strengths: Certificate valid, 89 days remaining; Issued by Let's Encrypt.
Recommended actions
2 items
Steps to improve terraform.io's security grade, ranked by impact.
1
Strengthen email authentication configuration
Email authentication is partially configured for terraform.io but has gaps. Actions needed: add SPF record; configure DKIM. 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
Add SPF record if missing: v=spf1 include:_spf.google.com -all
2
Configure DKIM and publish public key in DNS
3
Verify with: nslookup -type=txt _dmarc.terraform.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
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for terraform.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 terraform.io
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=reject
Strengths: DMARC policy set to reject (strongest). Issues: DMARC has no aggregate report URI (rua); No SPF record found; No DKIM records found for common selectors (may use non-standard selectors).
SPF Record
Missing
No SPF record found.
Security Headers
0/0 present
All headers configured.
HSTS
Not enabled
Could not fetch https://terraform.io — connection failed or timed out.
SSL Certificate
Valid
Strengths: Certificate valid, 89 days remaining; Issued by Let's Encrypt.
DNSSEC
Not enabled
Strengths: 4 nameservers configured (ns-1228.awsdns-25.org., ns-1672.awsdns-17.co.uk., ns-297.awsdns-37.com., ns-702.awsdns-23.net.); Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.