Skip to content
https://bible.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from Singapore, Singapore
302 Found
Checks
9
5 PASS 4 REVIEW
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
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 354 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your 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

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 354 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
# See https://nextjs.org/learn-pages-router/seo/crawling-and-indexing/robots-txt for documentation on how to use the robots.txt file
#

User-Agent: *
Disallow: /bible/*/*/notes
Disallow: /search/users
Disallow: /*/search/users

Disallow: /search/plans
Disallow: /*/search/plans
Disallow: /usi/
Disallow: /aml/
Disallow: /as/
Disallow: /eo/
Disallow: /uz/
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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.bible.com/
200https://bible.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://bible.com/ https://bible.com/

Consistent

C
TLS Certificate Expiry & Recommendations
Action
24 days until leaf cert expires — 6 issues to address
REVIEW

Certificate validity

24
days left
0d 30d 60d 90d+
Renew soon — under 30 days remaining

Recommended actions

  • Renew certificate — 24 days remaining
  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • Add includeSubDomains to the HSTS directive
  • 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 Records
4 A records, 4 ms lookup
PASS
4 A records, 4 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 151.101.65.55, 151.101.193.55, 151.101.1.55, 151.101.129.55
Info::
No IPv6 (AAAA) records
Info::
8 nameserver(s) configured
Got: ns02.whoeverfindsgodfinds.life, dns3.p01.nsone.net, ns03.whoeverfindsgodfinds.life, ns04.whoeverfindsgodfinds.life, ns01.whoeverfindsgodfinds.life, dns2.p01.nsone.net, dns4.p01.nsone.net, dns1.p01.nsone.net
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: 4 ms
Got: 4 ms
A151.101.65.55, 151.101.193.55, 151.101.1.55, 151.101.129.55
AAAA
CNAME
NSns02.whoeverfindsgodfinds.life, dns3.p01.nsone.net, ns03.whoeverfindsgodfinds.life, ns04.whoeverfindsgodfinds.life, ns01.whoeverfindsgodfinds.life, dns2.p01.nsone.net, dns4.p01.nsone.net, dns1.p01.nsone.net
MX
0 bible-com.mail.protection.outlook.com
TXT
SPF v=spf1 include:spf.protection.outlook.com -all
_globalsign-domain-verification=diaVbcf8mvzO-vJ0AcaQXGnRb2NksYac2FCSQ4QH9N
_globalsign-domain-verification=L_flxYF-fTqMHpq3hal6uty1uEValhk3bdJtnCnRiZ
google-site-verification=VfF3jQz5GvsfmoJSl5dYc_2VJIBQMgR5wSUXXi3Ai-g
loaderio=4b01a69fe647d2e19c126c0aa0a9647c
tinfoil-site-verification: 87e9486eb7b3a9dd85441954da2f5923a5e8ed64=290e6846e1e7...
"v=spf1 include:spf.mandrillapp.com ?all"
MS=ms83814250
v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCrLHiExVd55zd/IQ/J/mRwSR...
toYFyJd/eGqcpbpE20/XvYqGiWnFLUjNI974WRGEBOe501xwN1fcmBmK7Ww19Bc9KozVZ1gaFjct1FfV...
1password-site-verification=WBAIVJ4ZCFFCNCTSAOFRCB2NWY
CAALookup not available with standard resolver
Resolved in 4 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), 14 ms total
PASS
1 redirect(s), 14 ms total
Info::
Single redirect
Got: https://bible.com → https://www.bible.com/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://bible.com

https://bible.com

7 ms · HTTP/1.1

302

https://www.bible.com/

7 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://bible.com3027 msHTTP/1.1nginx
2https://www.bible.com/2007 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

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

A+
Domain Intelligence
bible.com — via Network Solutions, LLC, 31 years, 6 months old, hosted on Fastly
PASS
bible.com — via Network Solutions, LLC, 31 years, 6 months old, hosted on Fastly
Info::
Domain registered until Mar 24, 2036 (10 years 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: Fastly
Got: AS54113
Domain expiry

3538 days

March 24, 2036

SSL certificate

24 days

Issued by Certainly

Domain age

31 years, 6 months

Registered March 23, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Fastly

ASN AS54113

151.101.129.55

Registrar

Network Solutions, LLC

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the TLS certificate or verify auto-renewal is working
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Network Solutions, LLC
Created March 23, 1995 (31 years, 6 months ago)
Expires March 24, 2036 (10 years)
Last Updated March 25, 2026
Name Servers dns2.p03.nsone.net, dns3.p03.nsone.net, ns01.whoeverfindsgodfinds.life, ns03.whoeverfindsgodfinds.life
DNSSEC Not enabled
Hosting
IP Address 151.101.129.55
ASN AS54113 (FASTLY - Fastly, Inc., US)
Provider Fastly
Data source: rdap (0.5s)

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

Connection waterfall

DNS Lookup 2 ms TCP Connect 1 ms TLS Handshake 3 ms Server Processing 1 ms Content Transfer 0 ms
A+
CDN & Delivery
Fastly (HIT)
PASS
Fastly (HIT)
Info::
Site is served via Fastly CDN
Got: x-served-by: cache-sin-wsat1880098-SIN
Info::
CDN cache status: HIT
CDN Detected: Fastly
Provider Fastly Cache Status HIT Evidence x-served-by: cache-sin-wsat1880098-SIN
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback