Is iana.org safe to use as a vendor?

iana.org scored 85/100 on LynxRadar's security posture assessment. The domain meets baseline security requirements. 13 checks passed, 1 warnings, 1 critical issues across 15 passive checks including TLS, DMARC, security headers, breaches, and CVEs.

What TLS version does iana.org use?

iana.org uses TLSv1.3 with TLS_AES_256_GCM_SHA384. TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.

Does iana.org have SPF configured?

Yes. SPF record: v=spf1 redirect=icann.org

Does iana.org have security headers configured?

iana.org has 4 of 5 recommended security headers. Present: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy. Missing: Permissions-Policy.

Does iana.org use HSTS?

Yes. HSTS enabled: max-age=48211200s (558 days). Missing includeSubDomains — subdomains not covered. preload present.

Has iana.org been involved in a data breach?

No known breaches found. No known breaches found in public disclosure databases.

Does iana.org have known CVE vulnerabilities?

Detected technologies: Apache. No version information exposed — CVE matching not possible (this is good practice).

Is iana.org's SSL certificate valid?

Yes. 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.

Does iana.org have DNSSEC enabled?

Yes. 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.

iana.org Security Report — Grade B (85/100)

Q: Does iana.org have DMARC configured?

Yes. iana.org's DMARC policy is set to 'none'. SPF record: yes. 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).

Trust rating

Good · 85/100

Procurement snapshot

1 critical finding identified — these point to architectural gaps, not just configuration tweaks.

Strengths

DNS CAA Records

TLS Configuration

TLS Protocol Support

DNS Configuration

Questions to ask

Confirm email authentication (SPF/DKIM/DMARC) rollout plans

Estimated remediation effort: 2–5 days

Based on a passive external scan — supplement with vendor-provided attestations, not a replacement.

Trust Score Trend

→ No change 1 scan · Last scanned April 10, 2026

Your rating Industry average

Score

100 75 50 25 0

iana.org

85/100

Compliance & Certifications

Not yet verified

FedRAMP

ATO not on file

3rd party · 3PAO

Pro subscribers only

NIST 800-53

Not on file

Federal control baseline

Pro subscribers only

Incident History

None in 12 months

March 2026

ChatGPT data exposure

1 source

Resolved

Pro subscribers only

April 2023 – Feb 2026

ChatGPT data exposure

1 source

Resolved

Pro subscribers only

Security Posture

2 items need attention

13 passed

0 of 1 fixed

All 1 critical issue marked as fixed

Re-scan to confirm and update your score.

Turn on email authentication (SPF, DKIM, DMARC)

DMARC / Email Security

1–2 days

This exposes customers, partners, and employees to phishing attacks that impersonate your brand. Right now, anyone can send an email that looks like it came from [email protected] — no password or hack required. This is how the vast majority of phishing scams that impersonate a company work, and it can damage your reputation with customers even though your systems were never touched. Missing: DKIM.

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

1Turn on DKIM signing — look for "DKIM" under your email provider's admin/security settings. It will generate a record for you to paste into the same DNS settings above.

2After 2–4 weeks, check the DMARC reports for anything legitimate that got flagged, then tighten the policy from quarantine to reject.

Email authentication guide

Report unlocked.

View all 13 passed checks

DNS CAA Records

TLS Configuration

TLS Protocol Support

DNS Configuration

MX Records & Mail Provider

Cookie Security

HSTS Header

Security Headers

Known Breaches

security.txt (RFC 9116)

CVE Exposure

Certificate Hygiene

Subprocessors & Tech Stack

Company Signals

Claim profile →

Operational risk

Low

11 yrs operating. Well-funded

Lynxradar · Composite signal

Last funding

$40B

Series F · Mar 2025 · SoftBank-led

Crunchbase ↗

Employees

~3,000

+40% YoY growth

LinkedIn ↗

Trust Resources

Claim profile →

Trust Center

trust.iana.org ↗

Security page

iana.org/security ↗

iana.org/privacy ↗

DPA (Data Processing Agreement)

iana.org/dpa ↗

Updated recently

Subprocessors List

iana.org/policies/subprocessors ↗

Tech Stack Detected

Subprocessors

Cloudflare

Similar companies in Government / Public Sector

Appears in

Claim profile →

SOC 2 Type II certified vendors

847 companies · Updated weekly by LynxRadar

Track

ISO 27001 certified SaaS

312 companies · Updated weekly by LynxRadar

Track

Top AI vendors by trust score

94 companies · LynxRadar ranking

Track

Enterprise-ready SaaS · Trust score A or above

203 companies · LynxRadar ranking

Track

Blocking Issues

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).

Likelihood: ★★★★★

Impact: ★★★★☆

Medium Priority

Warn

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.

Likelihood: ★★☆☆☆

Impact: ★★★☆☆