Security checks — sorted by severity
DMARC / Email Security
Strengths: SPF record present. Issues: DMARC policy is 'none' (monitoring only, no enforcement); No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
Strengths: SPF record present. Issues: DMARC policy is 'none' (monitoring only, no enforcement); No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
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.
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.
MX Records & Mail Provider
Strengths: Mail handled by pechora1.icann.org; 4 MX record(s) configured; Multiple MX records provide redundancy; All MX records share the same priority (10) — round-robin load balancing (no primary/backup distinction).
Strengths: Mail handled by pechora1.icann.org; 4 MX record(s) configured; Multiple MX records provide redundancy; All MX records share the same priority (10) — round-robin load balancing (no primary/backup distinction).
DNS CAA Records
Strengths: CAA records configured (7 record(s)); Authorized CAs: pki.goog, sectigo.com, digicert.com, letsencrypt.org; Violation reporting (iodef) configured.
Strengths: CAA records configured (7 record(s)); Authorized CAs: pki.goog, sectigo.com, digicert.com, letsencrypt.org; Violation reporting (iodef) configured.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
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.
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.
DNS Configuration
Strengths: 4 nameservers configured (a.iana-servers.net., c.iana-servers.net., b.iana-servers.net., ns.icann.org.); 4 MX records present; DNSSEC enabled; Zone transfers properly restricted.
Strengths: 4 nameservers configured (a.iana-servers.net., c.iana-servers.net., b.iana-servers.net., ns.icann.org.); 4 MX records present; DNSSEC enabled; Zone transfers properly restricted.
Cookie Security
No cookies set on the homepage response. No cookie security flags to evaluate.
No cookies set on the homepage response. No cookie security flags to evaluate.
HSTS Header
HSTS enabled: max-age=48211200s (558 days). Missing includeSubDomains — subdomains not covered. preload present.
HSTS enabled: max-age=48211200s (558 days). Missing includeSubDomains — subdomains not covered. preload present.
Security Headers
4/5 security headers present. Missing: Permissions-Policy.
4/5 security headers present. Missing: Permissions-Policy.
Known Breaches
No known breaches found in public disclosure databases.
No known breaches found in public disclosure databases.
security.txt (RFC 9116)
Strengths: security.txt found with 6 field(s); Contact: https://hackerone.com/icann, mailto:[email protected]; Encryption key provided for secure reporting; Disclosure policy: https://www.icann.org/vulnerabilities; Canonical URL specified; Preferred languages: en, es, fr, ar, ru, zh. Issues: Missing 'Expires' field (required by RFC 9116); Not PGP signed (recommended for authenticity).
Strengths: security.txt found with 6 field(s); Contact: https://hackerone.com/icann, mailto:[email protected]; Encryption key provided for secure reporting; Disclosure policy: https://www.icann.org/vulnerabilities; Canonical URL specified; Preferred languages: en, es, fr, ar, ru, zh. Issues: Missing 'Expires' field (required by RFC 9116); Not PGP signed (recommended for authenticity).
CVE Exposure
Detected technologies: Apache. No version information exposed — CVE matching not possible (this is good practice).
Detected technologies: Apache. No version information exposed — CVE matching not possible (this is good practice).
Certificate Hygiene
Strengths: Certificate valid, 270 days remaining; Issued by Sectigo Limited. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.
Strengths: Certificate valid, 270 days remaining; Issued by Sectigo Limited. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.
Recommended actions
1 items
Steps to improve iana.org's security grade, ranked by impact.
1
Set up email authentication (DKIM)
Without email authentication, anyone can send emails that appear to come from iana.org. This is the most common vector for phishing attacks targeting employees and customers. DKIM is not configured.
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
AI Summary
What this means
iana.org scored 85/100, demonstrating a strong security posture. Minor improvements are noted below.
Critical gaps in: DMARC / Email Security. Positive signals: MX Records & Mail Provider, DNS CAA Records, TLS Configuration all passed.
1 action item 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 iana.org compares
Grade distribution across 2678 companies we've scanned. iana.org scores better than 78% of them.
88
A+
28
A
194
A-
200
B+
75
B
376
B-
137
C+
117
C
347
C-
123
D+
96
D
265
D-
632
F
iana.org — Grade B (85/100)
2678 companies scanned
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=none
Strengths: SPF record present. Issues: DMARC policy is 'none' (monitoring only, no enforcement); No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
SPF Record
Present
v=spf1 redirect=icann.org
Security Headers
4/5 present
Missing: Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=48211200s (558 days). Missing includeSubDomains — subdomains not covered. preload present.
SSL Certificate
Valid
Strengths: Certificate valid, 270 days remaining; Issued by Sectigo Limited. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.
DNSSEC
Enabled
Strengths: 4 nameservers configured (a.iana-servers.net., c.iana-servers.net., b.iana-servers.net., ns.icann.org.); 4 MX records present; DNSSEC enabled; Zone transfers properly restricted.
Similar companies
Other domains with comparable security profiles.
