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

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
96
GRADE
A
FIX
0
REVIEW
2
PASS
7
INFO
0
Probed from Amsterdam, Netherlands
200 OK
Checks
9
7 PASS 2 REVIEW
B
DNS Records
2 A records, 35 ms lookup
REVIEW
2 A records, 35 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 172.64.144.162, 104.18.43.94
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2a06:98c1:3102::ac40:90a2, 2606:4700:440c::6812:2b5e
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.okta.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: 35 ms
Got: 35 ms
A172.64.144.162, 104.18.43.94
AAAA2a06:98c1:3102::ac40:90a2, 2606:4700:440c::6812:2b5e
CNAMEwww.okta.com.cdn.cloudflare.net
NS
MX
TXT
CAALookup not available with standard resolver
Resolved in 35 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)

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

Certificate validity

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

Recommended actions

  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.okta.com

https://www.okta.com

64 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.okta.com20064 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2a06:98c1:3102::ac40:90a2, 2606:4700:440c::6812:2b5e
Got: 1 ms connect
IPv6 Ready
AAAA Records 2a06:98c1:3102::ac40:90a2, 2606:4700:440c::6812:2b5e Connection Reachable (1 ms)
A+
Crawlability
robots.txt present, sitemap with 2289 URLs
PASS
robots.txt present, sitemap with 2289 URLs
Info::
robots.txt is present
Got: 2518 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 2289 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 2518 B Sitemaps referenced 24 User-agents *AdobeEdgeOptimize/1.0* Blocking No — crawling allowed
# For more information about the robots.txt standard, see:
# http://www.robotstxt.org/robotstxt.html

# User-agent: *
# Disallow: /

User-agent: *AdobeEdgeOptimize/1.0*
Allow: /

# CSS, JS, Images
Allow: /core/*.css$
Allow: /core/*.css?
Allow: /core/*.js$
Allow: /core/*.js?
Allow: /core/*.gif
Allow: /core/*.jpg
Allow: /core/*.jpeg
Allow: /core/*.png
Allow: /core/*.svg
Allow: /profiles/*.css$
Allow: /profiles/*.css?
Allow: /profiles/*.js$
Allow: /profiles/*.js?
Allow: /profiles/*.gif
Allow: /profiles/*.jpg
Allow: /profiles/*.jpeg
Allow: /profiles/*.png
Allow: /profiles/*.svg
# Directories
Disallow: /core/
Disallow: /profiles/
# Files
Disallow: /README.txt
Disallow: /web.config
# Paths (clean URLs)
Disallow: /admin/
Disallow: /comment/reply/
Disallow: /filter/tips
Disallow: /node/add/
Disallow: /search/
Disallow: /user/register/
Disallow: /user/password/
Disallow: /user/login/
Disallow: /user/logout/
# Paths (no clean URLs)
Disallow: /index.php/admin/
Disallow: /index.php/comment/reply/
Disallow: /index.php/filter/tips
Disallow: /index.php/node/add/
Disallow: /index.php/search/
Disallow: /index.php/user/password/
Disallow: /index.php/user/register/
Disallow: /index.php/user/login/
Disallow: /index.php/user/logout/
Disallow: /investor-nav/
Disallow: /integrations/?page=*
Disallow: /blog/?*page=*
Disallow: /press-room/*?page=*

Sitemap: https://www.okta.com/sitemap.xml
Sitemap: https://www.okta.com/jp/sitemap.xml
Sitemap: https://www.okta.com/nl/sitemap.xml
Sitemap: https://www.okta.com/uk/sitemap.xml
Sitemap: https://www.okta.com/fr/sitemap.xml
Sitemap: https://www.okta.com/de/sitemap.xml
Sitemap: https://www.okta.com/au/sitemap.xml
Sitemap: https://www.okta.com/sg/sitemap.xml
Sitemap: https://www.okta.com/kr/sitemap.xml

Sitemap: https://www.okta.com/sitemap-root.xml
Sitemap: https://www.okta.com/sitemap-aem.xml
Sitemap: https://www.okta.com/ja-jp/sitemap-aem.xml
Sitemap: https://www.okta.com/en-nl/sitemap-aem.xml
Sitemap: https://www.okta.com/en-gb/sitemap-aem.xml
Sitemap: https://www.okta.com/fr-fr/sitemap-aem.xml
Sitemap: https://www.okta.com/de-de/sitemap-aem.xml
Sitemap: https://www.okta.com/en-au/sitemap-aem.xml
Sitemap: https://www.okta.com/en-sg/sitemap-aem.xml
Sitemap: https://www.okta.com/ko-kr/sitemap-aem.xml
Sitemap: https://www.okta.com/en-se/sitemap-aem.xml

Sitemap: https://www.okta.com/es-mx/sitemap-aem.xml
Sitemap: https://www.okta.com/pt-br/sitemap-aem.xml
Sitemap: https://www.okta.com/es-es/sitemap-aem.xml
Sitemap: https://www.okta.com/en-ca/sitemap-aem.xml
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.okta.com/
301https://okta.com/

Preferred variant: www

HTTP → HTTPS

301http://www.okta.com/ https://www.okta.com/

Consistent

A+
Domain Intelligence
okta.com — via MarkMonitor Inc., 22 years, 1 months old, hosted on AWS
PASS
okta.com — via MarkMonitor Inc., 22 years, 1 months old, hosted on AWS
Info::
Domain registered until Jun 11, 2027 (1 years, 2 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: AWS
Got: AS16509
Domain expiry

298 days

June 11, 2027

SSL certificate

158 days

Issued by DigiCert Inc

Domain age

22 years, 1 months

Registered June 11, 2004

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

18.239.36.77

Registrar

MarkMonitor Inc.

Lock status unknown 8 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 June 11, 2004 (22 years, 1 months ago)
Expires June 11, 2027 (1 years, 2 months)
Last Updated May 11, 2025
Name Servers ns-1459.awsdns-54.org, ns-1563.awsdns-03.co.uk, ns-285.awsdns-35.com, ns-684.awsdns-21.net, ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com
DNSSEC Not enabled
Hosting
IP Address 18.239.36.77
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
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 61 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
9 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
7 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
49 ms
Total Time Total request time from DNS lookup through full response.
62 ms

Connection waterfall

DNS Lookup 9 ms TCP Connect 1 ms TLS Handshake 7 ms Server Processing 32 ms Content Transfer 13 ms
A+
CDN & Delivery
Cloudflare (HIT)
PASS
Cloudflare (HIT)
Info::
Site is served via Cloudflare CDN (edge: AMS)
Got: cf-ray: 9e8bdd4e3cc2f5c7-AMS
Info::
CDN cache status: HIT
CDN Detected: Cloudflare
Provider Cloudflare Cache Status HIT Evidence cf-ray: 9e8bdd4e3cc2f5c7-AMS
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback