Skip to content
https://servicenow.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Amsterdam, Netherlands
301 Moved Permanently
Checks
9
4 PASS 4 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

B
Redirect Chain
1 redirect(s), 1609 ms total
REVIEW
1 redirect(s), 1609 ms total
Info::
Single redirect
Got: https://servicenow.com → https://www.servicenow.com/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1609 ms total
Got: 1609 ms

https://servicenow.com

1594 ms · HTTP/1.1

301

https://www.servicenow.com/

15 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://servicenow.com3011594 msHTTP/1.1Apache
2https://www.servicenow.com/40315 msHTTP/1.1AkamaiGHost

See the visual redirect chain in the HTTP Probe tab →

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
Crawlability
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

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

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
1 A records, 15 ms lookup
PASS
1 A records, 15 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 54.69.183.231
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
6 nameserver(s) configured
Got: a1-65.akam.net, a11-66.akam.net, a12-67.akam.net, a13-64.akam.net, a24-65.akam.net, a26-66.akam.net
Info::
2 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 15 ms
Got: 15 ms
A54.69.183.231
AAAA
CNAME
NSa1-65.akam.net, a11-66.akam.net, a12-67.akam.net, a13-64.akam.net, a24-65.akam.net, a26-66.akam.net
MX
10 us-smtp-inbound-2.mimecast.com
10 us-smtp-inbound-1.mimecast.com
TXT
MS=ms70563485
matillion:servicenow-com-saml
_2etlut4benbom5gnx2496bxmtk87i98
_632riug7fd15qln60ft35pag5yvni8y
d0qfrdybddn0mhd1hxghj3g9lyh7bx1h
3a84dc17-f498-4b2b-a050-16fcb2a4f16d
SPF v=spf1 redirect=8sfr6god._spf._d.mim.ec
apple-domain-verification=8Ktb46akHliox09O
apple-domain-verification=PBiFCvTxGHJKonK7
docusign=679ba08f-29d5-410a-b0b1-874848b06d43
docusign=7e0d53f8-4551-4d53-a663-94da71c63b7e
docusign=f516a2d6-6fc2-4152-a19f-b1025c0f4fd7
jamf-site-verification=arbZHaRSVr9-N7ApLMcGJg
airtable-verification=93e34b507ed4a3c5df47d872d579a674
amazonses:rqGNRQuklbGEAi6lDPzHNo5G26BbhUo38JDQCP+sppM=
docker-verification=fde3af9f-2690-4080-a58f-92b1c4b1e193
miro-verification=02e724937b726db0f5b05dd9e992c3e8ab936edf
anthropic-domain-verification-850tvb=OQXZlgSADSMaGucnm6a8HS9P1
anthropic-domain-verification-fv0z7f=egIHbtj4VTCblwZaWV1M1db1k
auctor-ai-domain-verification-310kkg=zjolo9UcVOiMTKwlXGBZ3DyD6
auctor-ai-domain-verification-5gnjxa=AC0zQNiNu89nhIo2T3iOp5jWs
0FAD63F4B45A3420CC4F71462AA9A21E539A5D44C20DC5236ADE59435286AAC8
623ba5debd9c3ba8e84d6fbf614af85432b75ad7019bddaafe356000b789567b
webexdomainverification.2BIAB=7c28fc2d-a8ab-4d7b-a33f-6772764f6773
windsurf-verification=5_l9Qd472RehvrIPaoB7dBcjewPaGuBYKbkmbntB-N0=
windsurf-verification=GyGX7_gOi8tN7fSv-X391FueiLuPVoKYLUZtSmOyUhQ=
google-site-verification=4RDxrxC5SEf5f9UaOfUm5LjNP4v5lbJs3pSpUqzNDgY
google-site-verification=DGePEwkifuMrps1ISqaBy9_md3_BmO0_QSZRltqCzFM
google-site-verification=NSdlb-n7hvlWX4htZ0GcDN3o8L9MoY85VkEeK27EZEk
google-site-verification=ZJvFWYHAsJ4jtbKSZgMHXtQzhJbqZTs31Jt6MODa5sg
h1-domain-verification=rMXpSDx7KYLsyf1LSJkyZGMPqg3iPEKUs4bgwEPnp9ntLE3b
neat-pulse-domain-verification-PQXDV1N=25281da9-e493-4c73-b46f-a070479fa9b2
stripe-verification=81511f9478fdbb0f63829eeba398cb240c4a1421b16e139a97fa0c312a79...
XLQuFahIHhdwUv4XbSTaZiSi/jTlMooG48jNi4/YgU5/DMx8P5gWzarvJcOv8U/8ueCr2ztqQZzQxhd8...
ewtMUtYyLn8qW1QqKXUB/1clZ0K6+nGsTOplIWhSiZRulmLul0EtWYdUeIRUlrf5KLwGcNiQ1B3IR5HD...
Dynatrace-site-verification=9569c3c6-abbd-482e-99ad-34d88cc6e34a__np28kc5ehofs75...
adobe-idp-site-verification=3c123bfe1c92d02595eef6eae0ffe2905d56394c121c67309a74...
figma-domain-verification=8b2a94f2ee6ed1918977e240e8e8745160f0dad9f17e64adef7511...
CAALookup not available with standard resolver
Resolved in 15 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

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.

A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

403https://www.servicenow.com/
200https://servicenow.com/

HTTP → HTTPS

301http://servicenow.com/ https://servicenow.com

Consistent

A+
Domain Intelligence
servicenow.com — via CSC Corporate Domains, Inc., 30 years, 6 months old, hosted on AWS
PASS
servicenow.com — via CSC Corporate Domains, Inc., 30 years, 6 months old, hosted on AWS
Info::
Domain registered until Mar 7, 2033 (6 years, 11 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: CSC Corporate Domains, Inc.
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Info::
Hosting: AWS
Got: AS16509
Domain expiry

2427 days

March 7, 2033

SSL certificate

196 days

Issued by Amazon

Domain age

30 years, 6 months

Registered March 6, 1996

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

54.69.183.231

Registrar

CSC Corporate Domains, Inc.

Unlocked 6 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar CSC Corporate Domains, Inc.
Created March 6, 1996 (30 years, 6 months ago)
Expires March 7, 2033 (6 years, 11 months)
Last Updated February 10, 2026
Name Servers a1-65.akam.net, a11-66.akam.net, a12-67.akam.net, a13-64.akam.net, a24-65.akam.net, a26-66.akam.net
DNSSEC Enabled
Hosting
IP Address 54.69.183.231
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.4s)

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

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

Connection waterfall

DNS Lookup 3 ms TCP Connect 142 ms TLS Handshake 284 ms Server Processing 142 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