Skip to content
https://cancer.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 3 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.

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
URL Variants
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
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.cancer.org/
200https://cancer.org/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://cancer.org/ https://cancer.org/

Consistent

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

Certificate validity

73
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
A+
DNS Records
1 A records, 78 ms lookup
PASS
1 A records, 78 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 40.71.250.191
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns3-04.azure-dns.org, ns1-04.azure-dns.com, ns2-04.azure-dns.net, ns4-04.azure-dns.info
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: 78 ms
Got: 78 ms
A40.71.250.191
AAAA
CNAME
NSns3-04.azure-dns.org, ns1-04.azure-dns.com, ns2-04.azure-dns.net, ns4-04.azure-dns.info
MX
10 mx2.hc200635.iphmx.com
10 mx1.hc200635.iphmx.com
TXT
onx=ff6aba77-9a2f-4490-ad64-c325fb1cb78e
TZD2Q8UZCLNT73GG6OM245OW9VBGY7USL327STC9V
google-site-verification=moKbLj3ms9kKgs9Mosg4birGP4uL3kosvRCN-hBEiuM
apple-domain-verification=UBuXRbX1wqt6aBAL
google-site-verification=cS_KPfCVlVto6ezGYFsb4UFzle4XOF-FYp8fx8CVcXw
stripe-verification=CF7A0B86D810D4C96FA7E6BD3970472A252B7E188622F583F1BE0620201D...
SPF v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email include:outboundmail.con...
adobe-idp-site-verification=e69aa7950f076f64bbd50cf78d008a44a0737dee41ac500328c1...
jamf-site-verification=bCR99Ny3NPJpgEb_03mrVg
logmein-verification-code=e14b97a5-812d-482d-bc79-e718f67a0d5e
google-site-verification=EC9L3iOQPRB3f_z5JDkP6dnIPhzSOA4vao_5yjsq4qE
acsproxyprod.azurewebsites.net
canva-site-verification=qALYrkxMsQ-1eSuPGHadXw
SFMC-XMCMCXoQbxJo109i8OgphFGBKzG0-wK9gmGPv4l6
facebook-domain-verification=f3ac5pzjb7omdn0aac9cuwhsuuqbw3
onetrust-domain-verification=6260a0a6bf964d1881aa954ec95af136
_79rj93f3s12cb8nvukev4y9cdch4yyg
docusign=6db2a367-6cc5-4df6-937d-d25380dae68d
google-gws-recovery-domain-verification=52904069
sd82dgz56rlsyr69r3xj
adobe-aem-verification=qa.cancer.org/64216/543768/f1f67e16-fbc1-481c-8d16-95c4af...
CAALookup not available with standard resolver
Resolved in 78 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
Redirect Chain
1 redirect(s), 490 ms total
PASS
1 redirect(s), 490 ms total
Info::
Single redirect
Got: https://cancer.org → https://www.cancer.org/ (301)
Info::
WWW normalization redirect

https://cancer.org

412 ms · HTTP/1.1

301

https://www.cancer.org/

78 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://cancer.org301412 msHTTP/1.1Microsoft-IIS/10.0
2https://www.cancer.org/20078 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 3496 URLs
PASS
robots.txt present, sitemap with 3496 URLs
Info::
robots.txt is present
Got: 438 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 3496 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 438 B Sitemaps referenced 2 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /
Disallow: */content/cancer/en/cancer/understanding-cancer/glossary/glossary/
Disallow: */content/cancer/es/cancer/understanding-cancer/glossary/glossary/
Disallow: */cancer/understanding-cancer/glossary/glossary/
Disallow: */content/cancer/en/
Disallow: */content/cancer-staging/
Disallow: */content/dam/CRC/
Disallow: *?q=

Sitemap: https://www.cancer.org/sitemap.xml
Sitemap: https://www.cancer.org/es/sitemap.xml
A+
Domain Intelligence
cancer.org — via Network Solutions, LLC, 32 years old, hosted on Microsoft Azure
PASS
cancer.org — via Network Solutions, LLC, 32 years old, hosted on Microsoft Azure
Info::
Domain registered until Oct 5, 2029 (3 years, 6 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: Network Solutions, LLC
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: Microsoft Azure
Got: AS8075
Domain expiry

1207 days

October 5, 2029

SSL certificate

73 days

Issued by Sectigo Limited

Domain age

32 years

Registered October 6, 1994

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Microsoft Azure

ASN AS8075

40.71.250.191

Registrar

Network Solutions, LLC

Unlocked 4 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
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Network Solutions, LLC
Created October 6, 1994 (32 years ago)
Expires October 5, 2029 (3 years, 6 months)
Last Updated July 8, 2020
Name Servers ns3-04.azure-dns.org, ns1-04.azure-dns.com, ns2-04.azure-dns.net, ns4-04.azure-dns.info
DNSSEC Not enabled
Hosting
IP Address 40.71.250.191
ASN AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US)
Provider Microsoft Azure
Data source: rdap (0.4s)

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

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 435 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
33 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
98 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
204 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
435 ms
Total Time Total request time from DNS lookup through full response.
435 ms

Connection waterfall

DNS Lookup 33 ms TCP Connect 98 ms TLS Handshake 204 ms Server Processing 100 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