Skip to content
https://alz.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
0
REVIEW
4
PASS
4
INFO
1
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
4 PASS 4 REVIEW
B
Redirect Chain
1 redirect(s), 1154 ms total
REVIEW
1 redirect(s), 1154 ms total
Info::
Single redirect
Got: https://alz.org → https://www.alz.org/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1154 ms total
Got: 1154 ms

https://alz.org

511 ms · HTTP/1.1

301

https://www.alz.org/

643 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://alz.org301511 msHTTP/1.1
2https://www.alz.org/200643 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

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.alz.org/
200https://alz.org/

Inconsistent — duplicate content risk

HTTP → HTTPS

307http://alz.org/ → https://alz.org/

Use 301 (permanent) instead of 302 (temporary)

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

Certificate validity

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

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • 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
Azure CDN (CONFIG_NOCACHE)
REVIEW
Azure CDN (CONFIG_NOCACHE)
Info::
Site is served via Azure CDN CDN
Got: x-azure-ref: 20260421T213033Z-15b779f7b6csbcknhC1LON6vug0000000uq000000000075z
Info::
CDN cache status: CONFIG_NOCACHE
CDN Detected: Azure CDN
Provider Azure CDN Cache Status CONFIG_NOCACHE Evidence x-azure-ref: 20260421T213033Z-15b779f7b6csbcknhC1LON6vug0000000uq000000000075z
A+
DNS Records
1 A records, 91 ms lookup
PASS
1 A records, 91 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 150.171.109.215
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2603:1061:14:d5::1
Info::
2 nameserver(s) configured
Got: dilbert.ns.cloudflare.com, elly.ns.cloudflare.com
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: 91 ms
Got: 91 ms
A150.171.109.215
AAAA2603:1061:14:d5::1
CNAME—
NSdilbert.ns.cloudflare.com, elly.ns.cloudflare.com
MX
0 mx2.hc4902-17.iphmx.com
0 mx1.hc4902-17.iphmx.com
TXT
6c2z4dk8x7l31n0hy728lbjk2h8sh7wm
9flwgry4206c8rjky4c5dpw3l3f5xw1b
globalsign-domain-verification=912CAF519D90B73C7A0EAE46AF477305
_az7kd2m0it6hhdjquvx5j3acjrldgvr
1password-site-verification=MWZ4WTSXJZGM3GVNGEKN2AFREM
apple-domain-verification=mXWdxBj9VgP3RvQJ
rxgycm4lnfvsvltp4lfmq7tbg48yxhvp
globalsign-domain-verification=9D22C4CAED79C54083EE43C9EAA1962C
b6w4jwqtdj0ql82sz1pd715y0sm87j2g
MS=ms84262538
SPF v=spf1 ip4:170.146.221.105 ip4:38.71.197.40 ip4:170.146.221.104 ip4:170.146.221....
atlassian-domain-verification=C8/gMGMCENzQEJXIoufyHcQqnLfGDaHHmtKM5bOLXUdMqWgs/8...
anthropic-domain-verification-5sdnyt=ufE1pFIpRXZCUtgJdtUmOjiBS
smartsheet-site-validation=t3RuVQb6Qir-XfFkm3zqlaKtUs8Z4cnu
a6a95f7b7bdee330b2ef7e49b9bbb74b1d969cacc8528ee38c9771781431b218
1381EC3F87F311310009055E6BFAD1FE3174A254
as=1730140194
CAALookup not available with standard resolver
Resolved in 91 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+
IPv6 Readiness
IPv6 reachable (24 ms)
PASS
IPv6 reachable (24 ms)
Info::
IPv6 is configured and reachable at 2603:1061:14:d5::1
Got: 24 ms connect
IPv6 Ready
AAAA Records 2603:1061:14:d5::1 Connection Reachable (24 ms)
A+
Crawlability
robots.txt present, sitemap with 3468 URLs
PASS
robots.txt present, sitemap with 3468 URLs
Info::
robots.txt is present
Got: 43 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 3468 entries
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 43 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
Disallow: /cmsctx/

User-agent: *

Allow: /
sitemap.xml 200 OK
Type URL Set URLs 3468 entries Valid XML Yes
Sample URLs:
A
HTTP Probe Timing
Total 560 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
38 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
24 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
52 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
560 ms
Total Time Total request time from DNS lookup through full response.
560 ms

Connection waterfall

DNS Lookup 38 ms TCP Connect 24 ms TLS Handshake 52 ms Server Processing 446 ms Content Transfer 0 ms
Domain Intelligence
Domain intelligence data not available
INFO
Domain intelligence data not available

RDAP and WHOIS lookup both failed

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback