Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Probed from Madrid, Spain

301 Moved Permanently

Checks

5 PASS 3 REVIEW 1 FIX

CDN & Delivery

Action

No CDN detected

FIX

No CDN detected

A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.

No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

Redirect Chain

1 redirect(s), 1557 ms total

REVIEW

1 redirect(s), 1557 ms total

Single redirect

Got: https://dailykos.com → https://www.dailykos.com/ (301)

WWW normalization redirect

Redirect overhead: 1557 ms total

Got: 1557 ms

https://dailykos.com

8 ms · HTTP/1.1

301

https://www.dailykos.com/

1549 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://dailykos.com	301	8 ms	HTTP/1.1	nginx
2	https://www.dailykos.com/	200	1549 ms	HTTP/1.1	nginx

See the visual redirect chain in the HTTP Probe tab →

URL Variants

www/non-www, trailing slash, HTTP→HTTPS

REVIEW

www/non-www, trailing slash, HTTP→HTTPS

Both www and non-www versions serve content

Got: Both variants return 200 Expected: One variant 301-redirects to the other

HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.dailykos.com/

200https://dailykos.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://dailykos.com/ → https://dailykos.com/

Consistent

TLS Certificate Expiry & Recommendations

83 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

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

1 A records, 36 ms lookup

PASS

1 A records, 36 ms lookup

Resolves to 1 IPv4 address(es)

Got: 192.0.66.73

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

Has 1 IPv6 (AAAA) record(s)

Got: 2a04:fa87:fffd::c000:4249

4 nameserver(s) configured

Got: ns-1935.awsdns-49.co.uk, ns-1254.awsdns-28.org, ns-845.awsdns-41.net, ns-389.awsdns-48.com

4 mail exchanger(s) configured

CAA records not checked

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

SPF record present in TXT

DNS resolution time: 36 ms

Got: 36 ms

A	192.0.66.73
AAAA	2a04:fa87:fffd::c000:4249
CNAME	—
NS	ns-1935.awsdns-49.co.uk, ns-1254.awsdns-28.org, ns-845.awsdns-41.net, ns-389.awsdns-48.com
MX	10 aspmx.l.google.com 20 alt2.aspmx.l.google.com 20 alt1.aspmx.l.google.com 30 aspmx2.googlemail.com
TXT	_globalsign-domain-verification=KcFPNTrfWf0ezsW4mywMdHLte8ArxFOLYKPL47eiGg google-site-verification=ZoMAUPpBeDNCWi3WykX48IojNx-Qi1blQvwFIKyfBgg google-site-verification=X47CqbkQYjt4pCk7A7rtUARaVNbp0AMPSg0cMf5TmEU google-site-verification=EM_V9xN4R98NTKX5l9WSFRQjFmoXZ0czXvFTgUcKBkM SPF v=spf1 +mx +include:_spf.google.com +include:sendgrid.net +a:maila.m3.maas360.co... atlassian-sending-domain-verification=6417605c-a99b-429e-bfbf-936c64df5a40 google-site-verification=axol8AUaDHTjIE46TcnrgfXasnfZhR75bhyF_K9Jtok stripe-verification=680222f3e095faf0f41229bc958737b943222cb2107289c125ba22043855... apple-domain-verification=wZ8Sub3ci8510FCp supertab-connect-verification=urn:stc:merchant:system:41ed5178-dc9b-4dc9-a49c-da... facebook-domain-verification=12isfkhq2vb5g9737gi6a6dwrryh55 atlassian-domain-verification=QnkmppBOgJDieGqR302fM3ARPsioieOpsZgCeqOJcRYrnJEXKx... google-site-verification=oozn0QjZeMM68fp1Ryv-v5XbH4ViJBRCKTFni3xR040
CAA	Lookup not available with standard resolver

Resolved in 36 ms

Multiple A records provide failover if one server goes down.

Why this matters

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.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A+

IPv6 Readiness

IPv6 reachable (0 ms)

PASS

IPv6 reachable (0 ms)

IPv6 is configured and reachable at 2a04:fa87:fffd::c000:4249

Got: 0 ms connect

IPv6 Ready

AAAA Records 2a04:fa87:fffd::c000:4249 Connection Reachable (0 ms)

A+

Crawlability

robots.txt present, sitemap with 8048 URLs

PASS

robots.txt present, sitemap with 8048 URLs

robots.txt is present

Got: 604 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 8048 entries

Sitemap index with 8048 child sitemaps

robots.txt references sitemap

robots.txt 200 OK

Size 604 B Sitemaps referenced 1 User-agents SemrushBot, SiteAuditBot, SemrushBot-BA, Amazonbot, GoogleOther, Meta-ExternalAgent, FacebookBot, rogerbot, DataForSeoBot, *, ClaudeBot, Google-Extended, barkrowler, dotbot, Applebot-Extended, CCBot, GPTBot, AhrefsBot, AhrefsSiteAudit Blocking No — crawling allowed

User-agent: *
Disallow: /wp-admin/
Disallow: /?s=
Allow: /wp-admin/admin-ajax.php

User-agent: Amazonbot
User-agent: Applebot-Extended
User-agent: CCBot
User-agent: ClaudeBot
User-agent: GPTBot
User-agent: Google-Extended
User-agent: GoogleOther
User-agent: Meta-ExternalAgent
User-agent: FacebookBot
Disallow: /

User-agent: AhrefsBot
User-agent: AhrefsSiteAudit
User-agent: barkrowler
User-agent: DataForSeoBot
User-agent: dotbot
User-agent: rogerbot
User-agent: SemrushBot
User-agent: SiteAuditBot
User-agent: SemrushBot-BA
Disallow: /
# Sitemap archive
Sitemap: https://www.dailykos.com/sitemap.xml

sitemap.xml 200 OK

Type Sitemap Index URLs 8048 entries Valid XML Yes

Child Sitemaps:

A+

Domain Intelligence

dailykos.com — via Amazon Registrar, Inc., 24 years, 2 months old

PASS

dailykos.com — via Amazon Registrar, Inc., 24 years, 2 months old

Domain registered until Sep 12, 2026 (4 months remaining)

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.

Registrar: Amazon Registrar, Inc.

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

62 days

September 12, 2026

SSL certificate

83 days

Issued by Let's Encrypt

Domain age

24 years, 2 months

Registered June 26, 2002

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2a04:fa87:fffd::c000:4249

Registrar

Amazon Registrar, Inc.

Unlocked 4 NS records

Expiry timeline

Today

+1 year

Domain expiry SSL expiry Danger zone (≤30 days)

Recommended actions

Renew the domain or enable auto-renewal to prevent accidental expiry
Enable DNSSEC to protect visitors from DNS spoofing
Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar Amazon Registrar, Inc.

Created June 26, 2002 (24 years, 2 months ago)

Expires September 12, 2026 (4 months)

Last Updated August 8, 2025

Name Servers ns-1254.awsdns-28.org, ns-1935.awsdns-49.co.uk, ns-389.awsdns-48.com, ns-845.awsdns-41.net

DNSSEC Not enabled

Hosting

IP Address 2a04:fa87:fffd::c000:4249

Data source: rdap (0.2s)

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 162 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

PASS

DNS Lookup

34 ms

TCP Connect

0 ms

TLS Handshake

3 ms

Time to First Byte

162 ms

Total Time

162 ms

Connection waterfall

DNS Lookup 34 ms TCP Connect 0 ms TLS Handshake 3 ms Server Processing 125 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.