Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations81 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
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 Records6 A records, 6 ms lookupPASS
| A | 172.67.75.80, 104.26.7.230, 104.26.6.230, 172.67.75.54, 172.67.75.57, 172.67.75.60 |
| AAAA | 2606:4700:20::ac43:4b3c, 2606:4700:20::ac43:4b39, 2606:4700:20::ac43:4b50, 2606:4700:20::681a:7e6, 2606:4700:20::ac43:4b36, 2606:4700:20::681a:6e6 |
| CNAME | — |
| NS | hope.ns.cloudflare.com, ned.ns.cloudflare.com |
| MX | 0 _dc-mx.a40d3fe26468.phoronix.com |
| TXT | google-site-verification=P51DaHZFBjisbYmRz99IaFr8LnDPbBbGW7arOPrueTI SPF v=spf1 ip4:190.102.104.130 +a +mx +ip4:192.211.48.82 ~all |
| 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.
ARedirect Chain1 redirect(s), 487 ms totalPASS
https://phoronix.com
161 ms · HTTP/1.1
https://www.phoronix.com/
326 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://phoronix.com | 301 | 161 ms | HTTP/1.1 | cloudflare |
| 2 | https://www.phoronix.com/ | 200 | 326 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
A+IPv6 ReadinessIPv6 reachable (1 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 20359 URLsPASS
User-agent: *
Disallow: /cgi-bin/
Disallow: /phxcms-admin/
Disallow: /xml/
Sitemap: https://www.phoronix.com/sitemap.php
User-agent: GPTBot
Disallow: /
User-agent: ChatGPT-User
Disallow: /
User-agent: CCBot
Disallow: /
User-agent: PerplexityBot
Disallow: /
User-agent: anthropic-ai
Disallow: /
User-agent: Claude-Web
Disallow: /
User-agent: ClaudeBot
Disallow: /
User-agent: meta-externalagent
Disallow: /
A+Domain Intelligencephoronix.com — via GoDaddy.com, LLC, 22 years, 2 months oldPASS
693 days
June 5, 2028
81 days
Issued by Google Trust Services
22 years, 2 months
Registered June 5, 2004
Not enabled
Protects against DNS spoofing
Unknown
2606:4700:20::ac43:4b36
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