Skip to content
https://suicidepreventionlifeline.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Santa Clara, United States
301 Moved Permanently
Checks
9
5 PASS 3 REVIEW 1 FIX
F
IPv6 Readiness
Action
IPv6 records exist but unreachable
FIX
IPv6 records exist but unreachable
Warning::
IPv6 DNS records exist but server is not reachable
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Got: 2606:4700:20::ac43:497f, 2606:4700:20::681a:e62, 2606:4700:20::681a:f62
Info::
IPv6 connection error
Got: dial tcp6 [2606:4700:20::ac43:497f]:443: connect: network is unreachable
IPv6 Misconfigured
AAAA Records 2606:4700:20::ac43:497f, 2606:4700:20::681a:e62, 2606:4700:20::681a:f62 Connection UNREACHABLE

Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.

Why this matters

Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.

Learn more

Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.

Source: RFC 8305 (Happy Eyeballs)

B
Redirect Chain
1 redirect(s), 1735 ms total
REVIEW
1 redirect(s), 1735 ms total
Info::
Single redirect
Got: https://suicidepreventionlifeline.org → https://988lifeline.org/ (301)
Warning::
Redirect overhead: 1735 ms total
Got: 1735 ms
Info::
Cross-domain redirect detected

https://suicidepreventionlifeline.org

43 ms · HTTP/1.1

301

https://988lifeline.org/

1693 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://suicidepreventionlifeline.org30143 msHTTP/1.1cloudflare
2https://988lifeline.org/2001693 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

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

Certificate validity

68
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: SJC)
Got: cf-ray: 9f077e38ad0b3884-SJC
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9f077e38ad0b3884-SJC
A+
DNS Records
3 A records, 17 ms lookup
PASS
3 A records, 17 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 104.26.15.98, 104.26.14.98, 172.67.73.127
Info::
Has 3 IPv6 (AAAA) record(s)
Got: 2606:4700:20::ac43:497f, 2606:4700:20::681a:e62, 2606:4700:20::681a:f62
Info::
2 nameserver(s) configured
Got: ivan.ns.cloudflare.com, lia.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: 17 ms
Got: 17 ms
A104.26.15.98, 104.26.14.98, 172.67.73.127
AAAA2606:4700:20::ac43:497f, 2606:4700:20::681a:e62, 2606:4700:20::681a:f62
CNAME
NSivan.ns.cloudflare.com, lia.ns.cloudflare.com
MX
0 suicidepreventionlifeline-org.mail.protection.outlook.com
TXT
MS=ms55089365
bnr5vcsrsd4rwjgm9h7k1q86ts3ftvmx
google-site-verification=el7qKkK7W1qOr5vPfSm2Z0-gL-uvuS88QjnYk2Q4r_0
gtt959pd8499rj3dqhlcldkmw9b5z3ty
qylg5b6sjl1f66scy65yt3tbsmd9gclx
SPF v=spf1 include:spf.protection.outlook.com -all
CAALookup not available with standard resolver
Resolved in 17 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+
Crawlability
robots.txt present, sitemap with 141 URLs
PASS
robots.txt present, sitemap with 141 URLs
Info::
robots.txt is present
Got: 161 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 141 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 161 B Sitemaps referenced 2 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php

Sitemap: https://988lifeline.org/sitemap.xml
Sitemap: https://988lifeline.org/es/sitemap.xml

A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

https://www.suicidepreventionlifeline.org/
200https://suicidepreventionlifeline.org/

HTTP → HTTPS

301http://suicidepreventionlifeline.org/ https://988lifeline.org/

Consistent

A+
Domain Intelligence
suicidepreventionlifeline.org — via Network Solutions, LLC, 21 years, 8 months old, hosted on Cloudflare
PASS
suicidepreventionlifeline.org — via Network Solutions, LLC, 21 years, 8 months old, hosted on Cloudflare
Info::
Domain registered until Dec 6, 2026 (7 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: Cloudflare
Got: AS13335
Domain expiry

143 days

December 6, 2026

SSL certificate

68 days

Issued by Let's Encrypt

Domain age

21 years, 8 months

Registered December 6, 2004

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

172.67.73.127

Registrar

Network Solutions, LLC

Unlocked 2 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 December 6, 2004 (21 years, 8 months ago)
Expires December 6, 2026 (7 months)
Last Updated October 12, 2025
Name Servers ivan.ns.cloudflare.com, lia.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 172.67.73.127
ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)
Provider Cloudflare
Data source: rdap (0.2s)

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

Connection waterfall

DNS Lookup 6 ms TCP Connect 5 ms TLS Handshake 11 ms Server Processing 8 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