Skip to main content
DNS Tool
Engineer's DNS Intelligence Report
Generated 9 Feb 2026, 01:42 UTC
Duration 18.7s
Integrity 2f1ef63ec861d49cf21e5ecf61af1667a4f9d9a7025b02ce327d01e7d8ed1ebca73d433c74b9f7033241533d8a6f1bedf1191c1826709027c5b2a07e333f9adf
Subject Domain
openai.com

Engineer's DNS Intelligence Report

openai.com
9 Feb 2026, 01:42 UTC · 18.7s · SHA-3-512: 2f1e✱✱✱✱ Verify
Executive Methodology
Recon Mode Snapshot Re-analyze New Domain
Footprint Azure DNS Google Workspace
DNS Security & Trust Posture
Risk Level: Secure
4 protocols configured, 4 not configured Why we go beyond letter grades
Suggested Scanner Configuration High Confidence
Based on 20 historical scans of this domain
Parameter Current Suggested Severity Rationale
timeout_seconds 5s 8s low Average scan duration is 31.9s, suggesting DNS responses are slow for this domain. Increasing timeout from 5s to 8s prevents premature resolution failures.
RFC 8767
Suggestions require explicit approval before applying. No automatic changes will be made.
Email Spoofing
Protected
Brand Impersonation
Protected
DNS Tampering
Enterprise
Certificate Control
Configured
Configured
DMARC (email spoofing protection), DKIM (4 selector(s), 2048-bit), CAA (certificate issuance restricted), BIMI (brand logo configured)
Not Configured
DNSSEC (DNS response signing), DANE not available on Google Workspace — deploy MTA-STS as the recommended transport security alternative, MTA-STS (email TLS policy), TLS-RPT (TLS delivery reporting)
Registrar (RDAP) LIVE
Markmonitor Inc. (Registrant: REDACTED REGISTRANT)
Where domain was purchased
Email Service Provider
Google Workspace
Email: Enabled
Web Hosting
Cloudflare
Where website is hosted
DNS Hosting
Azure DNS Enterprise
Where DNS records are edited
Email Security Methodology Can this domain be impersonated by email? No
Verdict: DMARC policy is reject - spoofed messages will be blocked by receiving servers. DKIM keys verified with strong cryptography.

SPF Record RFC 7208 §4 Verified

Does this domain declare who may send email on its behalf? Yes
Success -all 5/10 lookups

SPF valid with strict enforcement (-all), 5/10 lookups

v=spf1 include:_spf.google.com include:spf.protection.outlook.com include:8050860.spf04.hubspotemail.net include:mktomail.com include:spf_c.oraclecloud.com -all
RFC 7489 §10.1: -all may cause rejection before DMARC evaluation, preventing DKIM from being checked
RFC 7208 Conformant — This SPF record conforms to the syntax and semantics defined in RFC 7208 §4.
RFC Failure Mode: Unlike DMARC (where unknown tags are silently ignored per RFC 7489 §6.3), SPF with unrecognized mechanisms produces a PermError per RFC 7208 §4.6 — the record fails loudly rather than silently.
Related CVEs: CVE-2024-7208 (multi-tenant domain spoofing), CVE-2024-7209 (shared SPF exploitation), CVE-2023-51764 (SMTP smuggling bypasses SPF)
SPF hard fail (-all): compliance-strong, but can short-circuit DMARC. RFC 7489 notes that -all can cause some receivers to reject mail during the SMTP transaction — before DKIM is checked and before DMARC can evaluate the result. A message that would pass DMARC via DKIM alignment may be rejected prematurely. For most domains, ~all + DMARC p=reject is the strongest compatible posture — it allows every authentication method (SPF, DKIM, DMARC) to be fully evaluated before a decision is made.
DMARC is set to reject — enforcement is strong. However, some receivers may still reject messages on SPF hard fail before DKIM alignment is checked. Switching to ~all + p=reject would provide the same enforcement with full DMARC compatibility.

DMARC Policy RFC 7489 §6.3 Verified

Are spoofed emails rejected or quarantined? Yes — reject policy
Success p=reject

DMARC policy reject (100%) - excellent protection

v=DMARC1; p=reject; rua=mailto:tdfyvl0n@ag.dmarcian.com; ruf=mailto:tdfyvl0n@fr.dmarcian.com; fo=1; aspf=r
Alignment: SPF relaxed DKIM relaxed
No np= tag (DMARCbis) — non-existent subdomains inherit p= policy but adding np=reject provides explicit protection against subdomain spoofing
Forensic reports (ruf) configured - many providers ignore these
Reported to Dmarcian
RFC 7489 Conformant — DMARC record conforms to RFC 7489 §6.3 with full enforcement.
DMARCbis (Pending): draft-ietf-dmarc-dmarcbis will elevate DMARC to Standards Track, obsolete RFC 7489, replace pct= with t= (testing flag), add np= (non-existent subdomain policy), and mandate DNS tree walk for policy discovery instead of the Public Suffix List.
Related CVEs: CVE-2024-49040 (Exchange sender spoofing), CVE-2024-7208 (multi-tenant DMARC bypass)

DKIM Records RFC 6376 §3.6 Verified

Are outbound emails cryptographically signed? Yes — verified
Found 2048-bit

Found DKIM for 4 selector(s) with strong keys (2048-bit)

google._domainkey Google Workspace 2048-bit
v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCEWYrzXyOSGkTNJiMCNfZ3715I9vNAUQliUAmkTq/Kh9uZ/vVFTuYnokoaKwwkh/06vftmPEhqAE+sLLJAnoOeETUodcQT52EBCEYVV1T9rogJbO5kqjWxDJLNspH8vf1Yf3tmWQnVTY8ukqVjONL2NJDCW8H4328bHJw0CQxFwwIDAQAB
s1._domainkey SendGrid
k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA3uq4fmmiXKekB7UOJ1k1MIe3/S4h2KjDI8PkK1M3aUQ1B1D1ZJso5RhIsnrv2tCs6LgQXxHuOmL8IaHZl90TdDuxhu+hhKchPvCODWkhCW0T+05dGdKzE80icL5xGIKBP3BMFu7s7DrP9r+E1qZACvvwoEECj3wzddBuim6czFcEwoyonl6QSFZky/LWy4zrbmmng" "Y1VFNPyzosErbUqW3Ui9xd/URxbdNp5zZCsNr1UC1QNG9Tk/7LHpY7n9pQpyPUErz8Nq79nav3NgKaboVbhLITcqvzT5SQPB575ysNv6wCPqGXGZMJggKBnmho7NhO0EUz61WHBMq+QBLn+awIDAQAB
s2._domainkey SendGrid 2048-bit
k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDWLwDlB3/Mub6nqAlomkKrshuWid0wJCX/fi+1HKA1evbVx6GyKc0T9WvMFnrFi/jMVKrPIVDa6SeXkj7Yd/WjMzymadu3NcNgHhTlY3zLCqZu61wu3iqrVxMBX922/tcKjBMxwsczI8+dyuVQrShrrE5YfGVLVSnbbcTMPP+wRQIDAQAB
selector1._domainkey Microsoft 365 2048-bit
v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDBeqr8SdKZ1BqqiHxOtfPitBrMTPJe8UC0FpFtF77CvyaBfPqhUhN1N/HHstzLKq17IAcWpTlnZ//d8QZrmj+xxEo7ZGAvRp5HneG08qUIz1Ks4AdrvzfWA5yOFk9FLX/5otbtmjGPmynpi3JQLsez9Kf77Rd6U9XPN2rb7fGWjwIDAQAB;
RFC 6376 Conformant — DKIM keys and signatures conform to RFC 6376 §3.6 (Internet Standard).
Known Vulnerabilities: DKIM l= tag body length vulnerability (attacker appends unsigned content to signed mail), weak key exploitation (keys below 1024-bit are cryptographically breakable per RFC 6376 §3.3.3), DKIM replay attacks (re-sending legitimately signed messages at scale)

MTA-STS RFC 8461 §3 Verified

Can attackers downgrade SMTP to intercept mail? Not prevented
Warning

No MTA-STS record found

MTA-STS policy enforcement is evaluated in Mail Transport Security below.

TLS-RPT RFC 8460 §3 Verified

Will failures in TLS delivery be reported? No reporting
Warning

No TLS-RPT record found

Email Security Management Actively Managed

Intelligence: This domain uses dedicated email security management — indicating continuous monitoring and professional oversight, not a "set and forget" configuration. Reporting destinations reveal the operational security partner network, and we extract that intelligence directly from DNS.
Dmarcian
DMARC
DMARC aggregate reports (rua)
DANE / TLSA Verified Recon Methodology Can mail servers establish identity without a public CA? No
RFC 7672 §3 RFC 6698 §2 Not Available

DANE not available — Google Workspace does not support inbound DANE/TLSA on its MX infrastructure

DANE not deployable on Google Workspace

Google uses shared, multi-tenant MX infrastructure (aspmx.l.google.com) with certificate rotation. Google does not publish TLSA records for its MX hosts and does not allow customers to do so. Google also does not validate DANE/TLSA when sending outbound mail.

Recommended alternative: MTA-STS

Email Transport Security

Two mechanisms protect email in transit. DANE is the primary standard; MTA-STS is the alternative for domains that cannot deploy DNSSEC:

  • DNSSEC + DANE (RFC 7672) — Cryptographic chain of trust from DNS root to mail server certificate. Eliminates reliance on certificate authorities. No trust-on-first-use weakness. Requires DNSSEC.
  • MTA-STS (RFC 8461) — HTTPS-based policy requiring TLS for mail delivery. Works without DNSSEC but relies on CA trust and is vulnerable on first use (§10). Created for domains where “deploying DNSSEC is undesirable or impractical” (§2).
This domain has neither DANE nor MTA-STS. Since Google Workspace does not support inbound DANE, deploy MTA-STS (RFC 8461) to enforce TLS and protect against downgrade attacks.

Industry trend: Microsoft Exchange Online enforces inbound DANE with DNSSEC (GA October 2024), and providers like Proton Mail and Fastmail also support DANE. Google Workspace does not support DANE and relies on MTA-STS. Both mechanisms coexist because DANE is backward-compatible — senders skip the check if the domain isn't DNSSEC-signed (RFC 7672 §1.3).

Brand Security Can this brand be convincingly faked?
Verdict: Attackers cannot easily spoof your logo or obtain fraudulent TLS certificates.

BIMI BIMI Spec Verified Success VMC SVG

Is the brand identity verified and displayed in inboxes? Yes

BIMI with VMC certificate (from Verified CA)

VMC certificate accessible (from Verified CA) - logo displays in Gmail, Apple Mail, and all major providers.
v=BIMI1;l=https://openai.com/.well-known/bimi/openai_opco_llc_1207717866.svg;a=https://openai.com/.well-known/bimi/openai_opco_llc_1207717866.pem
BIMI Logo
Logo validated (SVG) View full logo

CAA RFC 8659 §4 Verified Success

Does this domain restrict who can issue TLS certificates? Yes

CAA configured - only cansignhttpexchanges=yes, godaddy.com, DigiCert, Let's Encrypt, Sectigo, Amazon can issue certificates (including wildcards)

Authorized CAs: cansignhttpexchanges=yes godaddy.com DigiCert Let's Encrypt Sectigo Amazon
0 issue "pki.goog; cansignhttpexchanges=yes"
0 issuewild "amazon.com"
0 issue "letsencrypt.org"
0 issuewild "digicert.com; cansignhttpexchanges=yes"
0 issuewild "sectigo.com"
0 issuewild "pki.goog; cansignhttpexchanges=yes"
0 issue "godaddy.com"
0 issue "digicert.com; cansignhttpexchanges=yes"
0 issue "sectigo.com"
0 issue "amazon.com"
0 issuewild "letsencrypt.org"
Since September 2025, all public CAs must verify domain control from multiple geographic locations (Multi-Perspective Issuance Corroboration, CA/B Forum Ballot SC-067). CAA records are now checked from multiple network perspectives before certificate issuance.
Domain Security Methodology Can DNS responses be tampered with in transit?
Verdict: Delegation is verified but DNS responses are unsigned and could be spoofed.

DNSSEC RFC 4033 §2 Verified Unsigned

DNSSEC not configured - DNS responses are unsigned

Alternative Security: Azure DNS provides enterprise-grade DNS with DDoS protection and monitoring.
Azure DNS (enterprise DNS with DDoS protection), CAA records (certificate issuance control)

NS Delegation Verified

4 nameserver(s) configured

Nameservers: ns1-02.azure-dns.com ns2-02.azure-dns.net ns3-02.azure-dns.org ns4-02.azure-dns.info
Multi-Resolver Verification Recon: Consensus reached - 4 resolvers (Cloudflare, Google, Quad9, OpenDNS, DNS4EU) agree on DNS records
Traffic & Routing Where does this domain's traffic actually terminate?

AIPv4 Address

104.18.33.45
172.64.154.211
Where the domain points for web traffic

AAAAIPv6 Address

No AAAA records
IPv6 not configured

MXMail Servers

5 alt1.aspmx.l.google.com.
10 alt3.aspmx.l.google.com.
5 alt2.aspmx.l.google.com.
1 aspmx.l.google.com.
10 alt4.aspmx.l.google.com.
Priority + mail server for email delivery
Google Workspace

SRVServices

No SRV records
No service-specific routing configured
Web: Reachable (2 IPv4, 0 IPv6) Mail: 5 servers Services: None
Subdomain Discovery RFC 6962 Recon UNAVAILABLE What subdomains and infrastructure are exposed in certificate logs? Unavailable
How did we find these?

Certificate Transparency log query timed out. The CT log service (crt.sh) may be experiencing high load. Re-analyze the domain to try again.

Δ No Propagation Issues: All DNS records are synchronized between resolver and authoritative nameserver.
DNS Intelligence What does DNS look like right now — and what changed over time?
DNS Evidence Diff Side-by-side comparison
Resolver Records (Public DNS cache)
Authoritative Records (Source of truth)
A 2 / 0 records
104.18.33.45
—
172.64.154.211
—
AAAA 0 / 0 records
No records
No records
CAA RFC 8659 §4 11 / 0 records
0 issue "digicert.com; cansignhttpexchanges=yes"
—
0 issuewild "letsencrypt.org"
—
0 issue "letsencrypt.org"
—
0 issuewild "amazon.com"
—
0 issue "godaddy.com"
—
0 issuewild "digicert.com; cansignhttpexchanges=yes"
—
0 issuewild "sectigo.com"
—
0 issue "amazon.com"
—
0 issuewild "pki.goog; cansignhttpexchanges=yes"
—
0 issue "sectigo.com"
—
0 issue "pki.goog; cansignhttpexchanges=yes"
—
DMARC _dmarc.openai.com RFC 7489 §6.3 1 / 0 records
v=DMARC1; p=reject; rua=mailto:tdfyvl0n@ag.dmarcian.com; ruf=mailto:tdfyvl0n@fr.dmarcian.com; fo=1; aspf=r
—
MTA-STS _mta-sts.openai.com RFC 8461 §3 0 / 0 records
No records
No records
MX RFC 5321 5 / 0 records
5 alt1.aspmx.l.google.com.
—
10 alt3.aspmx.l.google.com.
—
5 alt2.aspmx.l.google.com.
—
1 aspmx.l.google.com.
—
10 alt4.aspmx.l.google.com.
—
NS RFC 1035 4 / 0 records
ns4-02.azure-dns.info.
—
ns2-02.azure-dns.net.
—
ns3-02.azure-dns.org.
—
ns1-02.azure-dns.com.
—
SOA RFC 1035 1 / 0 records
ns1-02.azure-dns.com. azuredns-hostmaster.microsoft.com. 1 3600 300 2419200 300
—
TLS-RPT _smtp._tls.openai.com RFC 8460 §3 0 / 0 records
No records
No records
TXT RFC 7208 §4 39 / 0 records
mgverify=22d53df776e7e9198e72a000c4056f5ba1624b8f2a50e3d0f4925fcea15bb5d4
—
tukj3psjdk
—
airtable-verification=dea7eaaa4d90e623ec30a9b2fa12ca5f
—
twilio-domain-verification=c7745eae53aa58c5874d7a8508c510bc
—
dropbox-domain-verification=mra9n6toqbqj
—
hubspot-developer-verification=NDFmMGNmMTYtZWYxNS00YTNlLWFkM2ItMjEwYzhmYTk0NTNi
—
smartsheet-site-validation=b4J2lcr0i94a3_8qW2jIQxWjyqlGUmF1
—
canva-site-verification=3pgWM7c4EwmBo5rsy9b2Mg
—
google-site-verification=9sG4lDm5hmXEmnwpVGkId_ftzq-b84TYi0rwy9J-f9s
—
stripe-verification=b1d42b65d1782470604a6dbb360e9dfe8bd7426974e5110605e86b22d945288d
—
wrike-verification=NjMwNjgwMjo0NmU2YjQ1NjgzNGJkN2M3MmYwNWUyMTNhOWUwOGY0OTQxYjBlNWJmZTEwYjYzOWU5MDNlMDlkYzAxNGZlZDRh
—
atlassian-domain-verification=xdHUKPdNqeX/XU/VMyGIRWfzqvhwWmcHR1DhX2J3JllvjIY3A0Aw9Ctst0DXGIgt
—
box-domain-verification=e2ecedffb7ea6f02e5f7a4afdbb83e2892f81db3acd85ff600633ad76096d459
—
openai-domain-verification=dv-un30neQJyISDPkxgKgArFtEc
—
ZOOM_verify_Ji3VecODDwjBgU1GccqGAC
—
calendly-site-verification=fBZScJDPHrHKIWIb9dKdryZqPPcCkxGISR8z5xSdX
—
google-site-verification=BDCE3pqO3BG5T5jWaEmQl10f5gqe3GAXgjyV0pmA5Jo
—
figma-domain-verification=274542735efe890a700405d9916de07a971b531a0d1595c237b09d68770febf4-1762810003
—
apple-domain-verification=EgaXvYuVUgRwJTk3
—
pylon-domain-verification-na3cfk=bYVknYT5uGxjut616RQY8fCHj
—
hiAwXiKX20HcM9FtFK90WRyUFLSV1w
—
postman-domain-verification=dc3e890ca92455e54d07dcec9ea8404fc401b0a5a900dfb759062cd1dc68b28f7bc7db58254e4936ff8a9303f38cb9719e1af16757b09e0067c635510c90cde8
—
uber-domain-verification=faf07776-4ec9-4fd0-9ac5-2a6f8c514318
—
parsec-domain-verification=td_30Hu4AtBG9pDT9HTJCFK42bxN3q
—
linear-domain-verification=83vxugur897f
—
whimsical=a3593eda7e8523a75b01fd953cac04549faefe0c
—
airalo-domain-verification=xFzIMCLQ9JTlUFK
—
MS=ms50231473
—
v=spf1 include:_spf.google.com include:spf.protection.outlook.com include:8050860.spf04.hubspotemail.net include:mktomail.com include:spf_c.oraclecloud.com -all
—
ms-domain-verification=a14381d7-1e61-4cbf-97fa-4ac14336f0cf
—
onetrust-domain-verification=6bfaeb2a9cdf438bad3b7b30e745f3ed
—
onetrust-domain-verification=7acf44f596f84700bc82bfaaeb9b388c
—
notion-domain-verification=GZFdn3LQ77QuL3XKYZT6BmKDkFfmbiAorjzDIdvLRd6
—
google-site-verification=dU3pms6hgznfQnTCxkcq6P4jGjd8LMra0v429l4oElA
—
docker-verification=e315e0c2-f866-4bec-ac0c-844fa287bbec
—
jamf-site-verification=2ysWIpJrXkO40kW1SNc8Qg
—
miro-verification=0ee819554f4ff63f853affdf30d1cf76a15c6846
—
uber-domain-verification=77dfb7a6-1534-4c1b-a4e2-ba173fa8e9a3
—
atlassian-domain-verification=Q2BUDjXbr3zZaNROQ1MyCjvItM31fbzhL/GR5YEn96BAAyQzrQfkxaxxWC2qj/s5
—
DNS History Timeline BETA
Your key is sent directly to SecurityTrails and is never stored on our servers. Get an API key
DNS History Timeline BETA

When was a record added, removed, or changed — and could that change be the problem?

Analyze Another Domain

Confirm Your Email Configuration

This tool analyzes DNS records, but to verify actual email delivery, send a test email to Red Sift Investigate. Their tool shows exactly how your emails arrive, including SPF/DKIM/DMARC pass/fail results in the headers.

DATA FRESHNESS & METHODOLOGY

All security-critical records (SPF, DMARC, DKIM, DANE/TLSA, DNSSEC, MTA-STS, TLS-RPT, BIMI, CAA) are queried live from authoritative nameservers and cross-referenced against 5 independent public DNS resolvers (Cloudflare, Google, Quad9, OpenDNS, DNS4EU) at the time of each analysis. No security verdict uses cached data.

Registrar data (RDAP) is cached for up to 24 hours because domain ownership and registration details change infrequently. Certificate Transparency logs (subdomain discovery via RFC 6962) are cached for 1 hour because CT entries are append-only historical records. Sections using cached data are marked with a CACHED badge; live queries show LIVE.

Intelligence Sources

This analysis used 4 DNS resolvers (consensus), reverse DNS (PTR), Team Cymru (ASN attribution), IANA RDAP (registrar), crt.sh (CT logs), and SMTP probing (transport). All using open-standard protocols.

Full List
Verify Report Integrity SHA-3-512 Has this report been altered since generation? Verify below

This cryptographic hash seals the analysis data, domain, timestamp, and tool version into a tamper-evident fingerprint. Any modification to the report data will produce a different hash. This is distinct from the posture hash (used for drift detection) — the integrity hash uniquely identifies this specific report instance.

2f1ef63ec861d49cf21e5ecf61af1667a4f9d9a7025b02ce327d01e7d8ed1ebca73d433c74b9f7033241533d8a6f1bedf1191c1826709027c5b2a07e333f9adf
Evaluations reference 12 RFCs. Methods are reproducible using the verification commands provided. Results reflect DNS state at 9 Feb 2026, 01:42 UTC.
Download Raw Intelligence Download Checksum (.sha3)

Download the intelligence dump and verify its integrity, like you would a Kali ISO or any critical artifact. The SHA-3-512 checksum covers every byte of the download — deterministic serialization ensures identical hashes across downloads.

After downloading, verify with any of these commands:

Tip: cd ~/Downloads first (or wherever you saved the files).

OpenSSL + Sidecar (macOS, Linux, WSL) 
cat dns-intelligence-openai.com.json.sha3 && echo '---' && openssl dgst -sha3-512 dns-intelligence-openai.com.json
Python 3 (cross-platform) 
python3 -c "import hashlib; print(hashlib.sha3_512(open('dns-intelligence-openai.com.json','rb').read()).hexdigest())"
sha3sum (coreutils 9+) 
sha3sum -a 512 dns-intelligence-openai.com.json
Compare the output against the .sha3 file or the checksum API at /api/analysis/435/checksum. Hash algorithm: SHA-3-512 (Keccak, NIST FIPS 202).

Every finding in this report is backed by DNS queries you can run yourself. These vetted one-liners reproduce the exact checks used to build this report for openai.com. Our analysis adds multi-resolver consensus, RFC-based evaluation, and cross-referencing — but the underlying data is always independently verifiable. We are intelligence analysts, not gatekeepers.

DNS Records

Query A records (IPv4) RFC 1035 
dig +noall +answer openai.com A
Query AAAA records (IPv6) RFC 1035 
dig +noall +answer openai.com AAAA
Query MX records (mail servers) RFC 1035 
dig +noall +answer openai.com MX
Query NS records (nameservers) RFC 1035 
dig +noall +answer openai.com NS
Query TXT records RFC 1035 
dig +noall +answer openai.com TXT

Email Authentication

Check SPF record RFC 7208 
dig +short openai.com TXT | grep -i spf
Check DMARC policy RFC 7489 
dig +short _dmarc.openai.com TXT
Check DKIM key for selector 'google' RFC 6376 
dig +short google._domainkey.openai.com TXT
Check DKIM key for selector 's1' RFC 6376 
dig +short s1._domainkey.openai.com TXT
Check DKIM key for selector 's2' RFC 6376 
dig +short s2._domainkey.openai.com TXT
Check DKIM key for selector 'selector1' RFC 6376 
dig +short selector1._domainkey.openai.com TXT

Domain Security

Check DNSSEC DNSKEY records RFC 4035 
dig +dnssec +noall +answer openai.com DNSKEY
Check DNSSEC DS records RFC 4035 
dig +noall +answer openai.com DS
Validate DNSSEC chain (requires DNSSEC-validating resolver) RFC 4035 
dig +dnssec +cd openai.com A @1.1.1.1

Transport Security

Check TLSA record for alt1.aspmx.l.google.com RFC 7672 
dig +noall +answer _25._tcp.alt1.aspmx.l.google.com TLSA
Check TLSA record for alt3.aspmx.l.google.com RFC 7672 
dig +noall +answer _25._tcp.alt3.aspmx.l.google.com TLSA
Check TLSA record for alt2.aspmx.l.google.com RFC 7672 
dig +noall +answer _25._tcp.alt2.aspmx.l.google.com TLSA
Check TLSA record for aspmx.l.google.com RFC 7672 
dig +noall +answer _25._tcp.aspmx.l.google.com TLSA
Check TLSA record for alt4.aspmx.l.google.com RFC 7672 
dig +noall +answer _25._tcp.alt4.aspmx.l.google.com TLSA
Verify TLS certificate on primary MX (alt1.aspmx.l.google.com) RFC 6698 
openssl s_client -starttls smtp -connect alt1.aspmx.l.google.com:25 -servername alt1.aspmx.l.google.com 2>/dev/null | openssl x509 -noout -subject -dates
Check MTA-STS DNS record RFC 8461 
dig +short _mta-sts.openai.com TXT
Fetch MTA-STS policy file RFC 8461 
curl -sL https://mta-sts.openai.com/.well-known/mta-sts.txt
Check TLS-RPT record RFC 8460 
dig +short _smtp._tls.openai.com TXT

Brand & Trust

Check BIMI record BIMI Draft 
dig +short default._bimi.openai.com TXT
Check CAA records (certificate authority authorization) RFC 8659 
dig +noall +answer openai.com CAA

DNS Records

Check HTTPS/SVCB records RFC 9460 
dig +noall +answer openai.com HTTPS

Domain Security

Check CDS/CDNSKEY automation records RFC 7344 
dig +noall +answer openai.com CDS

Infrastructure Intelligence

RDAP domain registration lookup RFC 9083 
curl -sL 'https://rdap.org/domain/openai.com' | python3 -m json.tool | head -50

Transport Security

Test STARTTLS on primary MX (alt1.aspmx.l.google.com) RFC 3207 
openssl s_client -starttls smtp -connect alt1.aspmx.l.google.com:25 -servername alt1.aspmx.l.google.com </dev/null 2>/dev/null | head -5

Infrastructure Intelligence

Search Certificate Transparency logs RFC 6962 
curl -s 'https://crt.sh/?q=%25.openai.com&output=json' | python3 -c "import json,sys; [print(e['name_value']) for e in json.load(sys.stdin)]" | sort -u | head -20
Check security.txt RFC 9116 
curl -sL https://openai.com/.well-known/security.txt | head -20

AI Surface

Check for llms.txt 
curl -sI https://openai.com/llms.txt | head -5
Check robots.txt for AI crawler rules 
curl -s https://openai.com/robots.txt | grep -i -E 'GPTBot|ChatGPT|Claude|Anthropic|Google-Extended|CCBot|PerplexityBot'

Infrastructure Intelligence

ASN lookup for 104.18.33.45 (Team Cymru) 
dig +short 45.33.18.104.origin.asn.cymru.com TXT
ASN lookup for 172.64.154.211 (Team Cymru) 
dig +short 211.154.64.172.origin.asn.cymru.com TXT
Commands use dig, openssl, and curl — standard tools available on macOS, Linux, and WSL. Results may vary slightly due to DNS propagation timing and resolver caching.
Intelligence Confidence Audit Engine Verified · 9/9 Evaluated
How confident are these results? Each protocol is independently verified against RFC standards. No self-awarded badges.
SPF
Verified 4874 runs
DKIM
Verified 4692 runs
DMARC
Verified 4857 runs
DANE/TLSA
Verified 4676 runs
DNSSEC
Verified 4855 runs
BIMI
Verified 4691 runs
MTA-STS
Verified 4694 runs
TLS-RPT
Verified 4696 runs
CAA
Verified 4688 runs
Maturity: Development → Verified → Consistent → Gold → Gold Master

Appendix: Verification Commands

The core DNS queries behind this report can be independently verified using these standard terminal commands (dig, openssl, curl). DNS Tool adds multi-resolver consensus, RFC-based evaluation, and cross-referencing on top of the raw data shown here.

DNS Records

Query A records (IPv4) (RFC 1035) 
dig +noall +answer openai.com A
Query AAAA records (IPv6) (RFC 1035) 
dig +noall +answer openai.com AAAA
Query MX records (mail servers) (RFC 1035) 
dig +noall +answer openai.com MX
Query NS records (nameservers) (RFC 1035) 
dig +noall +answer openai.com NS
Query TXT records (RFC 1035) 
dig +noall +answer openai.com TXT

Email Authentication

Check SPF record (RFC 7208) 
dig +short openai.com TXT | grep -i spf
Check DMARC policy (RFC 7489) 
dig +short _dmarc.openai.com TXT
Check DKIM key for selector 'google' (RFC 6376) 
dig +short google._domainkey.openai.com TXT
Check DKIM key for selector 's1' (RFC 6376) 
dig +short s1._domainkey.openai.com TXT
Check DKIM key for selector 's2' (RFC 6376) 
dig +short s2._domainkey.openai.com TXT
Check DKIM key for selector 'selector1' (RFC 6376) 
dig +short selector1._domainkey.openai.com TXT

Domain Security

Check DNSSEC DNSKEY records (RFC 4035) 
dig +dnssec +noall +answer openai.com DNSKEY
Check DNSSEC DS records (RFC 4035) 
dig +noall +answer openai.com DS
Validate DNSSEC chain (requires DNSSEC-validating resolver) (RFC 4035) 
dig +dnssec +cd openai.com A @1.1.1.1

Transport Security

Check TLSA record for alt1.aspmx.l.google.com (RFC 7672) 
dig +noall +answer _25._tcp.alt1.aspmx.l.google.com TLSA
Check TLSA record for alt3.aspmx.l.google.com (RFC 7672) 
dig +noall +answer _25._tcp.alt3.aspmx.l.google.com TLSA
Check TLSA record for alt2.aspmx.l.google.com (RFC 7672) 
dig +noall +answer _25._tcp.alt2.aspmx.l.google.com TLSA
Check TLSA record for aspmx.l.google.com (RFC 7672) 
dig +noall +answer _25._tcp.aspmx.l.google.com TLSA
Check TLSA record for alt4.aspmx.l.google.com (RFC 7672) 
dig +noall +answer _25._tcp.alt4.aspmx.l.google.com TLSA
Verify TLS certificate on primary MX (alt1.aspmx.l.google.com) (RFC 6698) 
openssl s_client -starttls smtp -connect alt1.aspmx.l.google.com:25 -servername alt1.aspmx.l.google.com 2>/dev/null | openssl x509 -noout -subject -dates
Check MTA-STS DNS record (RFC 8461) 
dig +short _mta-sts.openai.com TXT
Fetch MTA-STS policy file (RFC 8461) 
curl -sL https://mta-sts.openai.com/.well-known/mta-sts.txt
Check TLS-RPT record (RFC 8460) 
dig +short _smtp._tls.openai.com TXT

Brand & Trust

Check BIMI record (BIMI Draft) 
dig +short default._bimi.openai.com TXT
Check CAA records (certificate authority authorization) (RFC 8659) 
dig +noall +answer openai.com CAA

DNS Records

Check HTTPS/SVCB records (RFC 9460) 
dig +noall +answer openai.com HTTPS

Domain Security

Check CDS/CDNSKEY automation records (RFC 7344) 
dig +noall +answer openai.com CDS

Infrastructure Intelligence

RDAP domain registration lookup (RFC 9083) 
curl -sL 'https://rdap.org/domain/openai.com' | python3 -m json.tool | head -50

Transport Security

Test STARTTLS on primary MX (alt1.aspmx.l.google.com) (RFC 3207) 
openssl s_client -starttls smtp -connect alt1.aspmx.l.google.com:25 -servername alt1.aspmx.l.google.com </dev/null 2>/dev/null | head -5

Infrastructure Intelligence

Search Certificate Transparency logs (RFC 6962) 
curl -s 'https://crt.sh/?q=%25.openai.com&output=json' | python3 -c "import json,sys; [print(e['name_value']) for e in json.load(sys.stdin)]" | sort -u | head -20
Check security.txt (RFC 9116) 
curl -sL https://openai.com/.well-known/security.txt | head -20

AI Surface

Check for llms.txt 
curl -sI https://openai.com/llms.txt | head -5
Check robots.txt for AI crawler rules 
curl -s https://openai.com/robots.txt | grep -i -E 'GPTBot|ChatGPT|Claude|Anthropic|Google-Extended|CCBot|PerplexityBot'

Infrastructure Intelligence

ASN lookup for 104.18.33.45 (Team Cymru) 
dig +short 45.33.18.104.origin.asn.cymru.com TXT
ASN lookup for 172.64.154.211 (Team Cymru) 
dig +short 211.154.64.172.origin.asn.cymru.com TXT
Running Multi-Source Intelligence Audit

openai.com

0s
DNS records — Cloudflare, Google, Quad9, OpenDNS, DNS4EU
Email auth — SPF, DMARC, DKIM selectors
DNSSEC chain of trust & DANE/TLSA
Certificate Transparency & subdomain discovery
SMTP transport & STARTTLS verification
MTA-STS, TLS-RPT, BIMI, CAA
Registrar & infrastructure analysis
Intelligence Classification & Interpretation

Every result includes terminal commands you can run to independently verify the underlying data. No proprietary magic.