Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BRedirect Chain2 redirect(s), 93 ms totalREVIEW
https://arcgis.com
53 ms · HTTP/1.1
https://www.arcgis.com/
21 ms · HTTP/1.1
https://www.arcgis.com/index.html
19 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://arcgis.com | 301 | 53 ms | HTTP/1.1 | ArcGIS Online |
| 2 | https://www.arcgis.com/ | 301 | 21 ms | HTTP/1.1 | ArcGIS Online |
| 3 | https://www.arcgis.com/index.html | 200 | 19 ms | HTTP/1.1 | ArcGIS Online |
See the visual redirect chain in the HTTP Probe tab →
Each redirect adds latency. Try to minimize the chain to 1 hop.
Redirect chain — each hop adds latency; combine into one redirect where possible.
Source: Google Search Central / web.dev
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BTLS Certificate Expiry & Recommendations216 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Add includeSubDomains to the HSTS directive
- Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
- Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+DNS Records4 A records, 11 ms lookupPASS
| A | 18.238.80.13, 18.238.80.17, 18.238.80.36, 18.238.80.80 |
| AAAA | — |
| CNAME | — |
| NS | ns-423.awsdns-52.com, ns-982.awsdns-58.net, ns-1062.awsdns-04.org, ns-1882.awsdns-43.co.uk |
| MX | 10 mxb-00151a02.gslb.pphosted.com 10 mxa-00151a02.gslb.pphosted.com |
| TXT | MS=ms57620037 2k3bb21l4zc0540m3gvspsr96jvmkb30 _nn8amovc4qu2n516mlp6jod1psa54uy rovag_verification_token=30E544ADF8FD41A2982A9D8FB663301A google-site-verification=XHlMyAfWOgYEki1Bc4oxFXq0wKm1FycJipsKmgr9dBc google-site-verification=jRCTo4scBhyphvqpN5eW0GLwVzrHxDj66tQbdk6LKzk SPF v=spf1 ip4:54.240.44.154 ip4:54.240.44.155 ip4:54.240.44.241 ip4:54.240.44.242 ~... postman-domain-verification=06ba9e1a9107cd23be82eb29957657a882b7e95e0ca5993bcec1... |
| CAA | Lookup not available with standard resolver |
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
A+Crawlabilityrobots.txt present, sitemap with 101 URLsPASS
User-agent: *
Sitemap: http://static.arcgis.com/sitemap.xml
- https://static.arcgis.com/sitemap1.xml
- https://static.arcgis.com/sitemap2.xml
- https://static.arcgis.com/sitemap3.xml
- https://static.arcgis.com/sitemap4.xml
- https://static.arcgis.com/sitemap5.xml
- https://static.arcgis.com/sitemap6.xml
- https://static.arcgis.com/sitemap7.xml
- https://static.arcgis.com/sitemap8.xml
- https://static.arcgis.com/sitemap9.xml
- https://static.arcgis.com/sitemap10.xml
- https://static.arcgis.com/sitemap11.xml
- https://static.arcgis.com/sitemap12.xml
- https://static.arcgis.com/sitemap13.xml
- https://static.arcgis.com/sitemap14.xml
- https://static.arcgis.com/sitemap15.xml
- https://static.arcgis.com/sitemap16.xml
- https://static.arcgis.com/sitemap17.xml
- https://static.arcgis.com/sitemap18.xml
- https://static.arcgis.com/sitemap19.xml
- https://static.arcgis.com/sitemap20.xml
- https://static.arcgis.com/sitemap21.xml
- https://static.arcgis.com/sitemap22.xml
- https://static.arcgis.com/sitemap23.xml
- https://static.arcgis.com/sitemap24.xml
- https://static.arcgis.com/sitemap25.xml
- https://static.arcgis.com/sitemap26.xml
- https://static.arcgis.com/sitemap27.xml
- https://static.arcgis.com/sitemap28.xml
- https://static.arcgis.com/sitemap29.xml
- https://static.arcgis.com/sitemap30.xml
- https://static.arcgis.com/sitemap31.xml
- https://static.arcgis.com/sitemap32.xml
- https://static.arcgis.com/sitemap33.xml
- https://static.arcgis.com/sitemap34.xml
- https://static.arcgis.com/sitemap35.xml
- https://static.arcgis.com/sitemap36.xml
- https://static.arcgis.com/sitemap37.xml
- https://static.arcgis.com/sitemap38.xml
- https://static.arcgis.com/sitemap39.xml
- https://static.arcgis.com/sitemap40.xml
- https://static.arcgis.com/sitemap41.xml
- https://static.arcgis.com/sitemap42.xml
- https://static.arcgis.com/sitemap43.xml
- https://static.arcgis.com/sitemap44.xml
- https://static.arcgis.com/sitemap45.xml
- https://static.arcgis.com/sitemap46.xml
- https://static.arcgis.com/sitemap47.xml
- https://static.arcgis.com/sitemap48.xml
- https://static.arcgis.com/sitemap49.xml
- https://static.arcgis.com/sitemap50.xml
- https://static.arcgis.com/sitemap51.xml
- https://static.arcgis.com/sitemap52.xml
- https://static.arcgis.com/sitemap53.xml
- https://static.arcgis.com/sitemap54.xml
- https://static.arcgis.com/sitemap55.xml
- https://static.arcgis.com/sitemap56.xml
- https://static.arcgis.com/sitemap57.xml
- https://static.arcgis.com/sitemap58.xml
- https://static.arcgis.com/sitemap59.xml
- https://static.arcgis.com/sitemap60.xml
- https://static.arcgis.com/sitemap61.xml
- https://static.arcgis.com/sitemap62.xml
- https://static.arcgis.com/sitemap63.xml
- https://static.arcgis.com/sitemap64.xml
- https://static.arcgis.com/sitemap65.xml
- https://static.arcgis.com/sitemap66.xml
- https://static.arcgis.com/sitemap67.xml
- https://static.arcgis.com/sitemap68.xml
- https://static.arcgis.com/sitemap69.xml
- https://static.arcgis.com/sitemap70.xml
- https://static.arcgis.com/sitemap71.xml
- https://static.arcgis.com/sitemap72.xml
- https://static.arcgis.com/sitemap73.xml
- https://static.arcgis.com/sitemap74.xml
- https://static.arcgis.com/sitemap75.xml
- https://static.arcgis.com/sitemap76.xml
- https://static.arcgis.com/sitemap77.xml
- https://static.arcgis.com/sitemap78.xml
- https://static.arcgis.com/sitemap79.xml
- https://static.arcgis.com/sitemap80.xml
- https://static.arcgis.com/sitemap81.xml
- https://static.arcgis.com/sitemap82.xml
- https://static.arcgis.com/sitemap83.xml
- https://static.arcgis.com/sitemap84.xml
- https://static.arcgis.com/sitemap85.xml
- https://static.arcgis.com/sitemap86.xml
- https://static.arcgis.com/sitemap87.xml
- https://static.arcgis.com/sitemap88.xml
- https://static.arcgis.com/sitemap89.xml
- https://static.arcgis.com/sitemap90.xml
- https://static.arcgis.com/sitemap91.xml
- https://static.arcgis.com/sitemap92.xml
- https://static.arcgis.com/sitemap93.xml
- https://static.arcgis.com/sitemap94.xml
- https://static.arcgis.com/sitemap95.xml
- https://static.arcgis.com/sitemap96.xml
- https://static.arcgis.com/sitemap97.xml
- https://static.arcgis.com/sitemap98.xml
- https://static.arcgis.com/sitemap99.xml
- https://static.arcgis.com/sitemap100.xml
- https://www.arcgis.com/apps/solutions/si...
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
ADomain Intelligencearcgis.com — via MarkMonitor Inc., 27 years, 2 months old, hosted on AWSPASS
EXPIRED
June 9, 2026
216 days
Issued by Amazon
27 years, 2 months
Registered June 9, 1999
Enabled
Protects against DNS spoofing
AWS
ASN AS16509
18.238.80.13
MarkMonitor Inc.
Expiry timeline
Recommended actions
- Domain has EXPIRED — renew immediately to avoid total site outage
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Consider enabling auto-renewal to prevent accidental expiration.
Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.
Source: ICANN renewal policy
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.
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