Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
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
- 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 Records1 A records, 5 ms lookupPASS
| A | 192.0.66.2 |
| AAAA | — |
| CNAME | — |
| NS | ns14.dnsmadeeasy.com, ns11.dnsmadeeasy.com, ns12.dnsmadeeasy.com, ns10.dnsmadeeasy.com, ns13.dnsmadeeasy.com, ns15.dnsmadeeasy.com |
| MX | 1 smtp.google.com |
| TXT | google-site-verification=odYJmF2MPtVL343j5Zlvwo2cjbkixWKHP3bGytnCJVU SPF v=spf1 a mx include:_spf.google.com ip4:70.36.151.60 ip4:168.235.224.0/24 includ... google-site-verification=I1Ek3br3WwYRcc5js5xG_ELtAfaJp_RXjNAXg7xMLBg google-site-verification=9SvJI7ZfkURoc8DVFBZdJyNMwX9dV1Zwt56xQU6ydCM 80F840E231 if3eccd3atscms774r7l4vm37i facebook-domain-verification=vy7lqzjkjynnu2b8gs7hmgxpcxwlqc MS=ms88475859 yahoo-verification-key=V73BrB3anKCzOErcXIS6EfHoKXyNusH1/MPysi/Sx+0= google-site-verification=JuQb_7vCzb0cjPCWwX24lT68UMuWMGZD_qjIgfHp63M BA8D310F9F emJH6FJJ3exdD3gvZqM+CYv3ql6BIcLoWB3v2GzHCqxXolPzTg5SpXJ0x5heupS1+cmIhxacYTBccrjy... |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.
Learn more ▾ ▴
Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.
Source: SRE practice / DNS architecture
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), 30 ms totalPASS
https://motherjones.com
21 ms · HTTP/1.1
https://www.motherjones.com/
9 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://motherjones.com | 301 | 21 ms | HTTP/1.1 | nginx |
| 2 | https://www.motherjones.com/ | 200 | 9 ms | HTTP/1.1 | nginx |
See the visual redirect chain in the HTTP Probe tab →
A+Crawlabilityrobots.txt present, sitemap with 2 URLsPASS
Sitemap: https://www.motherjones.com/sitemap.xml
Sitemap: https://www.motherjones.com/news-sitemap.xml
User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php
User-agent: Applebot-Extended
Disallow: /
User-agent: Amazonbot
Disallow: /
User-agent: anthropic-ai
Disallow: /
User-agent: Google-Extended
Disallow: /
User-agent: GPTBot
Disallow: /
User-agent: ChatGPT-User
Disallow: /
User-agent: ClaudeBot
Disallow: /
User-agent: cohere-ai
Disallow: /
User-agent: meta-externalagent
Disallow: /
User-agent: Perplexity-User
Disallow: /
A+Domain Intelligencemotherjones.com — via Network Solutions, LLC, 31 years, 3 months old, hosted on WordPress.com (Automattic)PASS
336 days
June 18, 2027
81 days
Issued by Let's Encrypt
31 years, 3 months
Registered June 19, 1995
Not enabled
Protects against DNS spoofing
WordPress.com (Automattic)
ASN AS2635
192.0.66.2
Network Solutions, 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