Skip to content
https://jezebel.com

Infrastructure

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

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://jezebel.com/ → https://www.jezebel.com/

Consistent

B
Domain Intelligence
jezebel.com — via GoDaddy.com, LLC, 30 years, 4 months old
REVIEW
jezebel.com — via GoDaddy.com, LLC, 30 years, 4 months old
Critical::
Domain expires in 28 days
This domain expires on May 21, 2026. Domains that expire accidentally cause complete website downtime. Enable auto-renewal or renew manually now.
Got: Expires May 21, 2026
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: GoDaddy.com, 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.
Domain expiry

EXPIRED

May 21, 2026

SSL certificate

69 days

Issued by Google Trust Services

Domain age

30 years, 4 months

Registered May 20, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700::6812:89c

Registrar

GoDaddy.com, LLC

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Domain has EXPIRED — renew immediately to avoid total site outage
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar GoDaddy.com, LLC
Created May 20, 1996 (30 years, 4 months ago)
Expires May 21, 2026 (28 days)
Last Updated May 21, 2025
Name Servers kehlani.ns.cloudflare.com, rodrigo.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700::6812:89c
Data source: rdap (0.2s)

This domain expires on May 21, 2026. Domains that expire accidentally cause complete website downtime. Enable auto-renewal or renew manually now.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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

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

Certificate validity

69
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: 9f079d701d0ad477-CDG
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9f079d701d0ad477-CDG
A+
DNS Records
2 A records, 52 ms lookup
PASS
2 A records, 52 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.18.9.156, 104.18.8.156
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700::6812:89c, 2606:4700::6812:99c
Info::
2 nameserver(s) configured
Got: kehlani.ns.cloudflare.com, rodrigo.ns.cloudflare.com
Info::
4 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: 52 ms
Got: 52 ms
A104.18.9.156, 104.18.8.156
AAAA2606:4700::6812:89c, 2606:4700::6812:99c
CNAME—
NSkehlani.ns.cloudflare.com, rodrigo.ns.cloudflare.com
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 aspmx2.googlemail.com
TXT
google-site-verification=5J62qP_NfV3r_wzR0VSuTog5NxCK1rorYeQLLRk9hfQ
_globalsign-domain-verification=63GY7DdhmEwU6Yc6mPqIRV6Tlu3atl9B6izj643Qy2
google-site-verification=wzLj7yPI-45i2HVYtGv2nT_GIShfwdSnvwW0IGdClpA
SPF v=spf1 a mx a:servers.mcsv.net include:_spf.google.com ~all
CAALookup not available with standard resolver
Resolved in 52 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), 180 ms total
PASS
1 redirect(s), 180 ms total
Info::
Single redirect
Got: https://jezebel.com → https://www.jezebel.com/ (301)
Info::
WWW normalization redirect

https://jezebel.com

58 ms · HTTP/1.1

301

https://www.jezebel.com/

123 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://jezebel.com30158 msHTTP/1.1cloudflare
2https://www.jezebel.com/200123 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:89c, 2606:4700::6812:99c
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700::6812:89c, 2606:4700::6812:99c Connection Reachable (17 ms)
A+
Crawlability
robots.txt present, sitemap with 129 URLs
PASS
robots.txt present, sitemap with 129 URLs
Info::
robots.txt is present
Got: 580 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 129 entries
Info::
Sitemap index with 129 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 580 B Sitemaps referenced 4 User-agents *, GPTBot, ChatGPT-User, Applebot-Extended Blocking No — crawling allowed

# START YOAST BLOCK
# ---------------------------
User-agent: *
Disallow: /wp-json/
Disallow: /?rest_route=

# ---------------------------
# END YOAST BLOCK

User-agent: GPTBot
Disallow: /
User-agent: ChatGPT-User
Disallow: /
User-agent: Applebot-Extended
Disallow: /
Sitemap:  https://www.jezebel.com/wp-content/site-maps/sitemap-index.xml
Sitemap:  https://www.jezebel.com/wp-content/site-maps/news-sitemap-index.xml
Sitemap:  https://www.jezebel.com/wp-content/site-maps/video-sitemap-index.xml
Sitemap:  https://www.jezebel.com/wp-content/site-maps/category-pages-sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 129 entries Valid XML Yes
Child Sitemaps:
A+
HTTP Probe Timing
Total 105 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
48 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.
22 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
106 ms
Total Time Total request time from DNS lookup through full response.
106 ms

Connection waterfall

DNS Lookup 48 ms TCP Connect 17 ms TLS Handshake 22 ms Server Processing 19 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