Skip to content
https://www.openai.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
89
GRADE
B
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from Madrid, Spain
308 Permanent Redirect
Checks
9
5 PASS 4 REVIEW
B
DNS Records
2 A records, 30 ms lookup
REVIEW
2 A records, 30 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.18.33.45, 172.64.154.211
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2a06:98c1:310d::6812:212d, 2a06:98c1:3103::ac40:9ad3
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: www.openai.com.cdn.cloudflare.net
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 30 ms
Got: 30 ms
A104.18.33.45, 172.64.154.211
AAAA2a06:98c1:310d::6812:212d, 2a06:98c1:3103::ac40:9ad3
CNAMEwww.openai.com.cdn.cloudflare.net
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 30 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more ▾

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

C
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.openai.com/
200https://openai.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

308http://www.openai.com/ → https://openai.com/

Use 301 (permanent) instead of 302 (temporary)

B
TLS Certificate Expiry & Recommendations
74 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

74
days left
0d 30d 60d 90d+

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • Enable DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
B
CDN & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: 9e8ba1bcaeec8048-CDG
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9e8ba1bcaeec8048-CDG
A
Redirect Chain
1 redirect(s), 323 ms total
PASS
1 redirect(s), 323 ms total
Info::
Single redirect
Got: https://www.openai.com → https://openai.com/ (308)
Info::
WWW normalization redirect

https://www.openai.com

62 ms · HTTP/1.1

308

https://openai.com/

261 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.openai.com30862 msHTTP/1.1cloudflare
2https://openai.com/200261 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (16 ms)
PASS
IPv6 reachable (16 ms)
Info::
IPv6 is configured and reachable at 2a06:98c1:310d::6812:212d, 2a06:98c1:3103::ac40:9ad3
Got: 16 ms connect
IPv6 Ready
AAAA Records 2a06:98c1:310d::6812:212d, 2a06:98c1:3103::ac40:9ad3 Connection Reachable (16 ms)
A+
Crawlability
robots.txt present, sitemap with 33 URLs
PASS
robots.txt present, sitemap with 33 URLs
Info::
robots.txt is present
Got: 98 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 33 entries
Info::
Sitemap index with 33 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 98 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /
Disallow: /microsoft-for-startups/

Sitemap: https://openai.com/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 33 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
openai.com — via MarkMonitor Inc., 19 years, 5 months old, hosted on Cloudflare
PASS
openai.com — via MarkMonitor Inc., 19 years, 5 months old, hosted on Cloudflare
Info::
Domain registered until Jan 19, 2029 (2 years, 9 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: MarkMonitor Inc.
Info::
Hosting: Cloudflare
Got: AS13335
Domain expiry

886 days

January 19, 2029

SSL certificate

74 days

Issued by Google Trust Services

Domain age

19 years, 5 months

Registered January 19, 2007

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

104.18.33.45

Registrar

MarkMonitor Inc.

Lock status unknown 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
Registrar MarkMonitor Inc.
Created January 19, 2007 (19 years, 5 months ago)
Expires January 19, 2029 (2 years, 9 months)
Last Updated October 17, 2024
Name Servers ns1-02.azure-dns.com, ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info
DNSSEC Not enabled
Hosting
IP Address 104.18.33.45
ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)
Provider Cloudflare
Data source: rdap (0.3s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more ▾

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

A+
HTTP Probe Timing
Total 92 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
33 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
17 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
22 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
93 ms
Total Time Total request time from DNS lookup through full response.
93 ms

Connection waterfall

DNS Lookup 33 ms TCP Connect 17 ms TLS Handshake 22 ms Server Processing 22 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback