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
CCrawlabilityActionrobots.txt present, sitemap with 66 URLsREVIEW
Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.
Disallow: / in robots.txt blocks every search crawler — the site becomes invisible in organic search.
Learn more ▾ ▴
Common deployment mistake: a staging robots.txt with `User-agent: * / Disallow: /` ships to prod. The site falls out of search results within days. Verify your robots.txt is the production-intended version. If this is intentional (private site), no action needed.
Source: Google Search Central
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
# --- Allowed bots with restrictions ---
User-agent: Googlebot
User-agent: Bingbot
User-agent: Googlebot-Image
User-agent: Bingbot-Image
User-agent: Slackbot
User-agent: Twitterbot
User-agent: facebookexternalhit
User-agent: Facebot
User-agent: LinkedInBot
User-agent: Discordbot
Disallow: /paper-copy/
Disallow: /pw/papercopy/
Disallow: /pw/papercopy_bestseller/
Disallow: /pw/by-topic/1-legacy/
Disallow: /cgi-bin/
Disallow: /pw/mobile/
Disallow: /iowa-edit/
Disallow: /binary-data/EGALLEY/
Disallow: /binary-data/DIY/
Disallow: /pw/bookit/
Disallow: /pw/search/
Disallow: /pw/emailtemplates/
# --- Block everything else ---
User-agent: *
Disallow: /
- http://www.publishersweekly.com/
- http://www.publishersweekly.com/pw/by-topic/industry-news/index.html
- http://www.publishersweekly.com/pw/by-topic/industry-news/financial-reporting/index.html
- http://www.publishersweekly.com/pw/by-topic/industry-news/bookselling/index.html
- http://www.publishersweekly.com/pw/by-topic/industry-news/publisher-news/index.html
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations136 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
Recommended actions
- Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
- 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, 38 ms lookupPASS
| A | 34.236.44.181, 44.221.143.107, 54.235.21.251, 52.44.83.226, 52.21.222.163, 54.87.182.39 |
| AAAA | — |
| CNAME | — |
| NS | ns-525.awsdns-01.net, ns-1999.awsdns-57.co.uk, ns-1370.awsdns-43.org, ns-190.awsdns-23.com |
| MX | 5 mx1-us1.ppe-hosted.com 10 mx2-us1.ppe-hosted.com |
| TXT | 1+xfSj66fDLMOBo3FU7jFXrl4sbzDAPzp7jNeHIyu3yxo4p+IfGkrnOXBBVK4Rhm1AiSeMwXOPlWvEQ1... ppe-68f6e42cfbad1b1a51c0 threatmate-dns-verification=TXT3425b1366f625864ad379dd4d19e45cd s7ft96aps4neuh2ll8stgu22jt MS=ms20322626 google-site-verification=hHlpwACqj4903pG75knIVp7PdkgPtn-67CwIkn78ZGo SPF v=spf1 include:spf.protection.outlook.com a:dispatch-us.ppe-hosted.com include:a... |
| 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), 955 ms totalPASS
https://publishersweekly.com
395 ms · HTTP/1.1
https://www.publishersweekly.com:443/
561 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://publishersweekly.com | 301 | 395 ms | HTTP/1.1 | awselb/2.0 |
| 2 | https://www.publishersweekly.com:443/ | 200 | 561 ms | HTTP/1.1 | nginx/1.6.2 |
See the visual redirect chain in the HTTP Probe tab →
A+Domain Intelligencepublishersweekly.com — via Network Solutions, LLC, 30 years, 5 months old, hosted on AWSPASS
290 days
April 2, 2027
136 days
Issued by Amazon
30 years, 5 months
Registered April 1, 1996
Not enabled
Protects against DNS spoofing
AWS
ASN AS14618
54.235.21.251
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