Skip to content
https://nfpa.org

Infrastructure

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

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://nfpa.org/ https://www.nfpa.org/

Consistent

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

Certificate validity

36
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
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: 9eff8b558b1d0248-CDG
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9eff8b558b1d0248-CDG
A+
DNS Records
2 A records, 116 ms lookup
PASS
2 A records, 116 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.18.3.98, 104.18.2.98
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700::6812:262, 2606:4700::6812:362
Info::
2 nameserver(s) configured
Got: leah.ns.cloudflare.com, osmar.ns.cloudflare.com
Info::
1 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: 116 ms
Got: 116 ms
A104.18.3.98, 104.18.2.98
AAAA2606:4700::6812:262, 2606:4700::6812:362
CNAME
NSleah.ns.cloudflare.com, osmar.ns.cloudflare.com
MX
0 nfpa-org.mail.protection.outlook.com
TXT
apple-domain-verification=RdHMIC4CBbrOIFlX
google-site-verification=FQ9YHh-o7JupdrRlORpZVHVRYGED9jueM-nlfrKQXjU
google-site-verification=lR8TkR-21Tt4tS4d7dt9_PUJKQINM7_48qwjP6k8118
bw=oJUT7v2chWRnIOt3Fbt6hSFlqIuPEc6hAmD5UeG/16wY
“k=rsa; p=AAAAB3NzaC1yc2EAAAADAQABAAAAgQDMTgr20i064SdTz+MFfBToJaiJRHZegnv YZDH...
ms-domain-verification=875b3078-4580-4f67-9797-2947c367589f
google-site-verification=hZDoxvW9i-2rXQMDaZ0gVCy6nOT_kNdG7nbjnWY9WF4
Dynatrace-site-verification=e2895d42-e448-4aa5-a6d1-7b6efe2c18ec__9n2v8gnjs5b47r...
ppe-d3f9e86ae04f2028485e85e9b7bb68719790605b
SPF v=spf1 include:spf1.nfpa.org include:_spf.salesforce.com include:aspmx.pardot.co...
400fde42-2b82-38d3-e063-0100007f7036
google-site-verification=KWyLmJmoMcMfAt7Auss-rqARAZJm8D7ex3znvG4uzH0
atlassian-domain-verification=6e0UBbA3aQwGQVgqW73bzCELVWyj0t2wbGyazSAFvMZWHBRPWf...
pinterest-site-verification=a8b081c016ed7a5c1f9f330f034b194b
I+6ylod910CZ7tXrBz2u4lcvlc9QB+hZ0EqWHeqZR8skjqdrDs9psNlOkCwRQLII Q/TYCQjK1kIhG2e...
atlassian-sending-domain-verification=2fa125d3-0295-42fd-9cc8-10c0aacf258c
pardot_14662_*=8af68f74a89c4d2822b75946266ca93c3e239f6156b8e812efd5506a84cb7c3b
sitecore-domain-verification=4813aeaa9b8f47bcbc6ab312b1b29533
CAALookup not available with standard resolver
Resolved in 116 ms

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), 346 ms total
PASS
1 redirect(s), 346 ms total
Info::
Single redirect
Got: https://nfpa.org → https://www.nfpa.org/ (301)
Info::
WWW normalization redirect

https://nfpa.org

66 ms · HTTP/1.1

301

https://www.nfpa.org/

280 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://nfpa.org30166 msHTTP/1.1cloudflare
2https://www.nfpa.org/200280 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700::6812:262, 2606:4700::6812:362
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700::6812:262, 2606:4700::6812:362 Connection Reachable (17 ms)
A
Crawlability
robots.txt present, no sitemap
PASS
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 467 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt references sitemap

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 200 OK
Size 467 B Sitemaps referenced 1 User-agents Googlebot, Googlebot-image, *, Storebot-Google Blocking No — crawling allowed
User-agent: *

Allow: /-/media/Project/Storefront/Catalog/Product Images/

Allow: /-/media/Project/Storefront/Catalog/Product-Images/

Allow: /-/media/project/storefront/catalog/product-images/

Disallow: /-/media/

Disallow: /ar/

Disallow: /en/

Disallow: /data/

Disallow: /standard_items/search_results


Sitemap: https://www.nfpa.org/sitemap.xml


User-agent: Storebot-Google

Disallow:

User-agent: Googlebot

Disallow:

User-agent: Googlebot-image

Disallow:
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

A+
HTTP Probe Timing
Total 101 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.
16 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
23 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
102 ms
Total Time Total request time from DNS lookup through full response.
102 ms

Connection waterfall

DNS Lookup 38 ms TCP Connect 16 ms TLS Handshake 23 ms Server Processing 24 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