Skip to content
https://christianpost.com

Infrastructure

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

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://christianpost.com/ https://christianpost.com/

Consistent

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

Certificate validity

33
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
2 A records, 48 ms lookup
PASS
2 A records, 48 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.21.77.9, 172.67.203.19
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:3031::6815:4d09, 2606:4700:3030::ac43:cb13
Info::
2 nameserver(s) configured
Got: karl.ns.cloudflare.com, liz.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: 48 ms
Got: 48 ms
A104.21.77.9, 172.67.203.19
AAAA2606:4700:3031::6815:4d09, 2606:4700:3030::ac43:cb13
CNAME
NSkarl.ns.cloudflare.com, liz.ns.cloudflare.com
MX
0 christianpost-com.mail.protection.outlook.com
TXT
facebook-domain-verification=j68jf4grzfp57oqi4w2kcizgc7d6m9
SPF v=spf1 mx include:spf.protection.outlook.com include:44647794.spf02.hubspotemail...
MS=ms61685899
google-site-verification=aIKh7pQ4_RU7FpwBsJIt7h-OBwOtuV5uOTemkhI3eFU
google-site-verification=CL65HV9JwOOtYMITNXIhAs20J2LQk1BFOWDI9qCBFU8
yahoo-verification-key=lGCvcz9Opc3gwWxRgcK/mIsUANwNltnHmn1sKjPjXy8=
google-site-verification=jUJZk866mtO5Gxkt7Qz98Q6XIzxevyn3ngdiSJLpP34
stripe-verification=69db225170818884830d1a24134f12f61fcee0bdad5cc7ab1066fd61c506...
facebook-domain-verification=9vimurabpq2rbjkaibkx06uckag7fi
google-site-verification=tMsErY9-S-pcV9ZqlKcg9hyyzxQxq8h9s8FRblIuWJk
google-site-verification=S0XaGNbAYamclRO7X-0-N6WgcO_uJs7ozV5rqMXCa3o
google-site-verification=61709tqwqibFdNyN3EFtGTWRuJlnPIIh5vgHQkC1GxE
google-site-verification=mwP9NfDknA9XnavdMQl9-1A6Z37wE19JMg9Mj0otLqE
CAALookup not available with standard resolver
Resolved in 48 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), 824 ms total
PASS
1 redirect(s), 824 ms total
Info::
Single redirect
Got: https://christianpost.com → https://www.christianpost.com/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 824 ms total
Got: 824 ms

https://christianpost.com

185 ms · HTTP/1.1

301

https://www.christianpost.com/

639 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://christianpost.com301185 msHTTP/1.1cloudflare
2https://www.christianpost.com/200639 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:3031::6815:4d09, 2606:4700:3030::ac43:cb13
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700:3031::6815:4d09, 2606:4700:3030::ac43:cb13 Connection Reachable (17 ms)
A+
Crawlability
robots.txt present, sitemap with 190 URLs
PASS
robots.txt present, sitemap with 190 URLs
Info::
robots.txt is present
Got: 1738 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 190 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 1738 B Sitemaps referenced 0 User-agents GPTBot, Amazonbot, Applebot-Extended, ClaudeBot, Google-Extended, meta-externalagent, *, Bytespider, CCBot, CloudflareBrowserRenderingCrawler Blocking No — crawling allowed
# As a condition of accessing this website, you agree to abide by the following
# content signals:

# (a)  If a Content-Signal = yes, you may collect content for the corresponding
#      use.
# (b)  If a Content-Signal = no, you may not collect content for the
#      corresponding use.
# (c)  If the website operator does not include a Content-Signal for a
#      corresponding use, the website operator neither grants nor restricts
#      permission via Content-Signal with respect to the corresponding use.

# The content signals and their meanings are:

# search:   building a search index and providing search results (e.g., returning
#           hyperlinks and short excerpts from your website's contents). Search does not
#           include providing AI-generated search summaries.
# ai-input: inputting content into one or more AI models (e.g., retrieval
#           augmented generation, grounding, or other real-time taking of content for
#           generative AI search answers).
# ai-train: training or fine-tuning AI models.

# ANY RESTRICTIONS EXPRESSED VIA CONTENT SIGNALS ARE EXPRESS RESERVATIONS OF
# RIGHTS UNDER ARTICLE 4 OF THE EUROPEAN UNION DIRECTIVE 2019/790 ON COPYRIGHT
# AND RELATED RIGHTS IN THE DIGITAL SINGLE MARKET.

# BEGIN Cloudflare Managed content

User-agent: *
Content-Signal: search=yes,ai-train=no
Allow: /

User-agent: Amazonbot
Disallow: /

User-agent: Applebot-Extended
Disallow: /

User-agent: Bytespider
Disallow: /

User-agent: CCBot
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: CloudflareBrowserRenderingCrawler
Disallow: /

User-agent: Google-Extended
Disallow: /

User-agent: GPTBot
Disallow: /

User-agent: meta-externalagent
Disallow: /

# END Cloudflare Managed Content


A+
Domain Intelligence
christianpost.com — via TLDS L.L.C. d/b/a SRSPlus, 25 years, 1 months old
PASS
christianpost.com — via TLDS L.L.C. d/b/a SRSPlus, 25 years, 1 months old
Info::
Domain registered until Jul 18, 2028 (2 years, 3 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: TLDS L.L.C. d/b/a SRSPlus
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.
Domain expiry

734 days

July 18, 2028

SSL certificate

33 days

Issued by Let's Encrypt

Domain age

25 years, 1 months

Registered July 18, 2001

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:3030::ac43:cb13

Registrar

TLDS L.L.C. d/b/a SRSPlus

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 TLDS L.L.C. d/b/a SRSPlus
Created July 18, 2001 (25 years, 1 months ago)
Expires July 18, 2028 (2 years, 3 months)
Last Updated February 25, 2026
Name Servers karl.ns.cloudflare.com, liz.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700:3030::ac43:cb13
Data source: rdap (0.1s)

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

Connection waterfall

DNS Lookup 47 ms TCP Connect 17 ms TLS Handshake 21 ms Server Processing 204 ms Content Transfer 0 ms
A
CDN & Delivery
Cloudflare (DYNAMIC)
PASS
Cloudflare (DYNAMIC)
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: 9f07ea1938e9b758-CDG
Info::
CDN cache status: DYNAMIC
CDN Detected: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: 9f07ea1938e9b758-CDG
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback