Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DRedirect ChainAction2 redirect(s), 1090 ms totalFIX
https://sans.org
496 ms · HTTP/1.1
https://www.sans.org/
311 ms · HTTP/1.1
https://www.sans.org/emea/
283 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://sans.org | 301 | 496 ms | HTTP/1.1 | |
| 2 | https://www.sans.org/ | 302 | 311 ms | HTTP/1.1 | |
| 3 | https://www.sans.org/emea/ | 200 | 283 ms | HTTP/1.1 |
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
If permanent, use 301 instead.
302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.
Learn more ▾ ▴
Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).
Source: Google Search Central
DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
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
CCrawlabilityActionrobots.txt present, sitemap with 0 URLsREVIEW
Search engines may not be able to parse the sitemap. Fix XML validation errors.
An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.
Learn more ▾ ▴
Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.
Source: sitemaps.org / Google Search Central
An empty sitemap provides no value. Add <url> entries for your pages.
An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.
Learn more ▾ ▴
Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.
Source: Google Search Central / sitemaps.org
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
<html style="height:100%"><head><META NAME="ROBOTS" CONTENT="NOINDEX, NOFOLLOW"><meta name="format-detection" content="telephone=no"><meta name="viewport" content="initial-scale=1.0"><meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1"><script type="text/javascript" src="/_Incapsula_Resource?SWJIYLWA=719d34d31c8e3a6e6fffd425f7e032f3"></script></head><body style="margin:0px;height:100%"><iframe id="main-iframe" src="/_Incapsula_Resource?SWUDNSAI=31&xinfo=9-10775380-0%202NNN%20RT%281776887860782%2095%29%20q%280%20-1%20-1%201%29%20r%280%20-1%29%20B12%2811%2c860970%2c0%29&incident_id=230000670061562736-56595080427213001&edet=12&cinfo=0b000000&rpinfo=0&cts=n%2bh4S9afDOY1WTHM6oB2vJ7%2bx2YE%2f%2fVnKq%2bIyzNzx8Hp9WYauCbAXPxxEJ%2fP%2bLBc&cip=141.227.188.119&mth=GET" frameborder=0 width="100%" height="100%" marginheight="0px" marginwidth="0px">Request unsuccessful. Incapsula incident ID: 230000670061562736-56595080427213001</iframe></body></html>
BTLS Certificate Expiry & Recommendations33 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
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+DNS Records2 A records, 83 ms lookupPASS
| A | 45.60.31.34, 45.60.103.34 |
| AAAA | — |
| CNAME | — |
| NS | ns-282.awsdns-35.com, ns-1746.awsdns-26.co.uk, ns-749.awsdns-29.net, ns-1270.awsdns-30.org |
| MX | 10 mxa-002c1802.gslb.pphosted.com 10 mxb-002c1802.gslb.pphosted.com |
| TXT | amazonses:s3qWj+9usSfVvw6sOrHcxcLqSLUHe4+xX2Bcz382ZY4= miro-verification=cb513e5bc26e25d81c0b82a55d647d153d95e378 atlassian-domain-verification=6NyU75cdG0l2wc7/BZnvjf0Vk6le6u8mecfnfsB0aAODfOm0qF... jetbrains-domain-verification=9d0spo0t1rbzwx801jejq5z9i SPF v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ~all YOfxOkgh96cLKDUd0042Sx/iL9bDXs/ZIJ11T2OczGY4TajTWwW8RXLmRajj6sSrD+sNdelF3pXA0PPm... dropbox-domain-verification=q0ksfx82ki2b parallels-domain-verification=d6efc2b9b49e46d292bb3257cf202b17fe4c8b0530e849e797... _globalsign-domain-verification=XbqPoFvyLnW1lHWyrKazU_F9bRAXRI-_SoC2KhQHxT globalsign-domain-verification=8363748754C0F878F4E36650604B623E pardot928673=573fbfb6e48d50fe412afebd0623144f1667d7fd7e780b3a403bca1493ef624e _globalsign-domain-verification=Z0fOVJB0oLvstFlL9BBVBnLszC-egXTqDZTeNuWdCx anthropic-domain-verification-d54pt1=NypbYImJLv9tPPkjFVZ4ohUN4 zapier-domain-verification-challenge=b166a197-0f75-4a5a-932e-8c66e7e10991 google-site-verification=qP6oSPKijvCWSIP7JqPOF_HuU0NmQX8NTC8Eln8hXMg status-page-domain-verification=2w964jh22625 asv=c92bd4107a8a4880020e898eef0586e7 canva-site-verification=SBkYH7bWYvbsjI0sPM-yIw apple-domain-verification=ZZoZ4NmnUelze8au jamf-site-verification=2ipudMToEuJ3J3ihrRVRlw MS=ms15381092 openai-domain-verification=dv-mQdOkfMBQ2VUSYimMob17Cj0 google-site-verification=fdFAbK_U8Wu9OJDEauVhmgZ0OuJxWA-P4DQhZGx3hjs |
| 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+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencesans.org — via DomainPeople, Inc., 31 years, 1 months old, hosted on INCAPSULA - Incapsula Inc, USPASS
381 days
August 3, 2027
33 days
Issued by GlobalSign nv-sa
31 years, 1 months
Registered August 4, 1995
Not enabled
Protects against DNS spoofing
INCAPSULA - Incapsula Inc, US
ASN AS19551
45.60.31.34
DomainPeople, Inc.
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
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
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