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.
BRedirect Chain1 redirect(s), 1115 ms totalREVIEW
https://seattlepi.com
1078 ms · HTTP/1.1
https://www.seattlepi.com/
38 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://seattlepi.com | 301 | 1078 ms | HTTP/1.1 | Apache/2.4.58 |
| 2 | https://www.seattlepi.com/ | 200 | 38 ms | HTTP/1.1 |
See the visual redirect chain in the HTTP Probe tab →
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
BCrawlabilityrobots.txt present, sitemap with 0 URLsREVIEW
Search engines may not be able to parse the sitemap. Fix XML validation errors.
An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.
Learn more ▾ ▴
Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.
Source: sitemaps.org / Google Search Central
An empty sitemap provides no value. Add <url> entries for your pages.
An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.
Learn more ▾ ▴
Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.
Source: Google Search Central / sitemaps.org
Sitemap: https://www.seattlepi.com/sitemap.xml
Sitemap: https://www.seattlepi.com/sitemap_news.xml
User-agent: ai2bot-dolma
User-agent: anthropic-ai
User-agent: applebot-extended
User-agent: bytespider
User-agent: ccbot
User-agent: claude-user
User-agent: claude-web
User-agent: claudebot
User-agent: cohere-ai
User-agent: diffbot
User-agent: duckassistbot
User-agent: friendlycrawler
User-agent: omgili
User-agent: omgilibot
User-agent: perplexity-user
User-agent: perplexitybot
User-agent: scrapy
User-agent: timpibot
User-agent: youbot
User-agent: webzio-extended
User-agent: kangaroo-bot
Disallow: /
User-agent: AmazonAdBot
Allow: /
User-agent: *
Disallow: /business/press-releases/
Disallow: /style/beauty/hearstmagazines/
Disallow: /style/fashion/hearstmagazines/
Disallow: /living/relationships/hearstmagazines/
Disallow: /homeandgarden/home/hearstmagazines/
Disallow: /living/wellness/hearstmagazines/
Disallow: /mockup/
Disallow: /search
Disallow: /technology/businessinsider/
Disallow: /413gkwMT/
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BHTTP Probe TimingTotal 1147 ms — DNS, TCP, TLS, TTFB, content transfer breakdownREVIEW
Connection waterfall
BTLS Certificate Expiry & Recommendations33 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
ADNS Records4 A records, 1066 ms lookupPASS
| A | 34.197.233.251, 34.198.86.45, 34.204.119.243, 34.235.224.231 |
| AAAA | — |
| CNAME | — |
| NS | ns1.hearstnp.com, ns6.hearstnp.com, ns5.hearstnp.com, ns4.hearstnp.com, ns3.hearstnp.com, ns2.hearstnp.com |
| MX | 10 seattlepi-com.mail.protection.outlook.com |
| TXT | tollbit-domain-verification=0b07466e4113da1379eb3d448c5bddc2a00686708f142a7c260a... google-site-verification=bcIXwgwdiCYxKi8bJuST1_aJEFKunUp_0CaIuKNKzS0 6iU5Ra8aKG7DarY5Jb66AdUCQXkm1ebvSJdbWxlPW5zJwaomqmBqgG2rRfgpWri6WT0ZlnaCPWH5yKRw... MS=ms58962836 BSI103498586397 facebook-domain-verification=icrkaur3pimrbkluwox983vgrqsc6b _globalsign-domain-verification=Iiihy-iv_vLdlIMtHvh-aCdqO2T53oCoknhW44njXn facebook-domain-verification=c93hqiadq77at28ozqa0086u6kcrrj adobe-idp-site-verification=3ebb0754e0941b0fd3e9cfe346802f5b6321a2a9bce74d7ffbce... google-site-verification=91ob8eyr5JpjdyHWmcNWWBECe3I22ernxeVfbHLOmg8 globalsign-domain-verification=KaParXxs1OHDy7o8CMbPpHBN-2m_mzwdPqKMMQ66a6 google-site-verification=4RqIe5IESs1uvGNGstnXhX95gzAtQxT8plJ-Nnf9gxA google-site-verification=KUJEgfM3X4ga-0QdFbsc65OyxUwwa3iu0Xuv9v8h0wc google-site-verification=biVGkUuP9VaLqfh038ISDvJCbMescMmpMcynWvUnOmA google-site-verification=sNO_w4ke0jKHh81PrThw2_bKGKIpJF_hE9FSydxHqYM google-site-verification=yJoBH5lkKR5UwBxMZUSz4d6yxTD9O8fGIv1WfXseFJQ google-site-verification=4kV5OSeX2iftotGA9dMzOWpo8izn6O7nMS_MaJaN_mg google-site-verification=af4olFmfc9Gi403QI3rbP2XZTm1vFOlHyEtAXkiLhHw 85d128ee2d21412fa477db6941750e5e google-site-verification=AV83Pxlph62VS0IDdL_V4qTb8hH332EO-qPXdbi3bZM SPF v=spf1 include:spf.protection.outlook.com include:mail.azure.localedge.com ip4:... |
| 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.
Slow DNS adds latency to every page load. Consider a faster DNS provider.
DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.
Source: DNS performance benchmarks
A+Domain Intelligenceseattlepi.com — via CSC Corporate Domains, Inc., 27 years, 5 months old, hosted on AWSPASS
253 days
March 25, 2027
33 days
Issued by Let's Encrypt
27 years, 5 months
Registered March 25, 1999
Not enabled
Protects against DNS spoofing
AWS
ASN AS14618
34.198.86.45
CSC Corporate Domains, Inc.
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