Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BTLS Certificate Expiry & Recommendations69 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- 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 Records2 A records, 8 ms lookupPASS
| A | 104.18.197.52, 104.18.198.52 |
| AAAA | 2606:4700::6812:c634, 2606:4700::6812:c534 |
| CNAME | — |
| NS | jason.ns.cloudflare.com, tara.ns.cloudflare.com |
| MX | 10 aspmx.l.google.com 20 alt1.aspmx.l.google.com 20 alt2.aspmx.l.google.com 30 aspmx3.googlemail.com 30 aspmx2.googlemail.com |
| TXT | 2a3f7189edffbbc5d3e608681978b0de MS=B168769AC8FCF1863C834779BD0735F2DBDA2E66 ahrefs-site-verification_30955a0f15475ddc52124a6d6766c9f3ad15a1ed79ae183bdf24dbd... ahrefs-site-verification_c24ee71e823434bec57cccad6b908b91744a6c5f3e5a02c051854e7... atlassian-domain-verification=m6kYOe7wSd65B3OgaHvFb0wiyu8rQq84MGoxJcVEBXtdfsdUjs... google-site-verification=67VVL0E-EylgvfVRaQdfyYc-tPW1BhebYlArItrBhqQ google-site-verification=D16g9kcBExCqb99IPfMp5aS2kJn38MqmwPdYI7ExHU8 google-site-verification=jqLjRcWVfGod6leLX4MAYWzbHX6W2Z5zpJ8nMqe3w_I loaderio=e1776a465a656132a33272089604f5e3 v=DMARC1; p=reject; sp=reject; rua=mailto:g8pvspca@ag.us.dmarcian.com,mailto:dma... SPF v=spf1 include:_spf.google.com include:sendgrid.net include:_spf.mailersend.net ... |
| CAA | Lookup not available with standard resolver |
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
A+Redirect ChainNo redirects — direct accessPASS
https://cointelegraph.com
195 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://cointelegraph.com | 200 | 195 ms | HTTP/1.1 | cloudflare |
A+IPv6 ReadinessIPv6 reachable (1 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 55 URLsPASS
User-Agent: *
Disallow: /search?*
Disallow: /api/
Disallow: /wp-admin/
Disallow: /wp-signup.php
Disallow: /public/index.php/
Disallow: /*/wp-login.php
Disallow: /profile
Disallow: /*?ref=
Disallow: /*_token=
Disallow: /*from=
Disallow: /*fbclid
Disallow: /*portalId
Disallow: /*_ga
Disallow: /*_twitter
Disallow: /*dates=*location=*
Disallow: /*per_page
Disallow: /amp*
Sitemap: https://cointelegraph.com/sitemap.xml
Sitemap: https://cointelegraph.com/sitemap-google-news.xml
- https://cointelegraph.com/sitemap/post-1...
- https://cointelegraph.com/sitemap/post-2...
- https://cointelegraph.com/sitemap/post-3...
- https://cointelegraph.com/sitemap/post-4...
- https://cointelegraph.com/sitemap/post-5...
- https://cointelegraph.com/sitemap/post-6...
- https://cointelegraph.com/sitemap/post-7...
- https://cointelegraph.com/sitemap/post-8...
- https://cointelegraph.com/sitemap/post-9...
- https://cointelegraph.com/sitemap/post-1...
- https://cointelegraph.com/sitemap/post-1...
- https://cointelegraph.com/sitemap/post-1...
- https://cointelegraph.com/sitemap/post-1...
- https://cointelegraph.com/sitemap/post-1...
- https://cointelegraph.com/sitemap/post-1...
- https://cointelegraph.com/sitemap/post-1...
- https://cointelegraph.com/sitemap/post-1...
- https://cointelegraph.com/sitemap/post-1...
- https://cointelegraph.com/sitemap/post-1...
- https://cointelegraph.com/sitemap/post-2...
- https://cointelegraph.com/sitemap/post-2...
- https://cointelegraph.com/sitemap/post-2...
- https://cointelegraph.com/sitemap/post-2...
- https://cointelegraph.com/sitemap/post-2...
- https://cointelegraph.com/sitemap/post-2...
- https://cointelegraph.com/sitemap/post-2...
- https://cointelegraph.com/sitemap/post-2...
- https://cointelegraph.com/sitemap/post-2...
- https://cointelegraph.com/sitemap/post-2...
- https://cointelegraph.com/sitemap/post-3...
- https://cointelegraph.com/sitemap/post-3...
- https://cointelegraph.com/sitemap/post-3...
- https://cointelegraph.com/sitemap/post-3...
- https://cointelegraph.com/sitemap/post-3...
- https://cointelegraph.com/sitemap/post-3...
- https://cointelegraph.com/sitemap/post-3...
- https://cointelegraph.com/sitemap/post-3...
- https://cointelegraph.com/sitemap/post-3...
- https://cointelegraph.com/sitemap/post-3...
- https://cointelegraph.com/sitemap/post-4...
- https://cointelegraph.com/sitemap/post-4...
- https://cointelegraph.com/sitemap/post-4...
- https://cointelegraph.com/sitemap/post-4...
- https://cointelegraph.com/sitemap/podcas...
- https://cointelegraph.com/magazine/sitem...
- https://cointelegraph.com/sitemap/conver...
- https://cointelegraph.com/sitemap/explai...
- https://cointelegraph.com/sitemap/author...
- https://cointelegraph.com/sitemap/tag-1....
- https://cointelegraph.com/sitemap/tag-2....
- https://cointelegraph.com/sitemap/catego...
- https://cointelegraph.com/sitemap/page.x...
- https://cointelegraph.com/sitemap/guide....
- https://cointelegraph.com/sitemap/price-...
- https://cointelegraph.com/sitemap-google...
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencecointelegraph.com — via GoDaddy.com, LLC, 12 years, 8 months oldPASS
1189 days
October 17, 2029
69 days
Issued by Google Trust Services
12 years, 8 months
Registered October 17, 2013
Not enabled
Protects against DNS spoofing
Unknown
2606:4700::6812:c534
GoDaddy.com, LLC
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
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.
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