Skip to content
https://nybooks.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
4 PASS 4 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
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.

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 1805 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 1805 B Sitemaps referenced 0 User-agents ImagesiftBot, Scrapy, TikTokSpider, iaskspider/2.0, meta-externalfetcher, PanguBot, Crawlspace, VelenPublicWebCrawler, DuckAssistBot, Claude-SearchBot, meta-externalagent, FriendlyCrawler, YouBot, AI2Bot, Googlebot-image, Applebot, ClaudeBot, cohere-training-data-crawler, Cotoyogi, SemrushBot-OCOB, NovaAct, Perplexity-User, Factset_spyderbot, FirecrawlAgent, cohere-ai, GoogleOther-Video, SemrushBot-SWA, *, GoogleOther-Image, imgproxy, Kangaroo Bot, PetalBot, Sidetrade indexer bot, Ai2Bot-Dolma, aiHitBot, Brightbot 1.0, Claude-Web, Meta-ExternalFetcher, omgili, Timpibot, anthropic-ai, Bytespider, ChatGPT-User, Diffbot, omgilibot, QualifiedBot, ICC-Crawler, ISSCyberRiskCrawler, OAI-SearchBot, CCBot, MistralAI-User/1.0, Operator, Google-CloudVertexBot, GPTBot, img2dataset, Meta-ExternalAgent, wpbot, Googlebot, Claude-User, Google-Extended, Webzio-Extended, PerplexityBot, FacebookBot, Amazonbot, Applebot-Extended, GoogleOther Blocking No — crawling allowed
User-agent: Googlebot
User-agent: Googlebot-image
Disallow: 
User-agent: *
Disallow: /wp-login.php*
Disallow: /_issue/*
Disallow: /*?printpage=true
Disallow: /account/signin/
Disallow: /search/
User-agent: AI2Bot
User-agent: Ai2Bot-Dolma
User-agent: aiHitBot
User-agent: Amazonbot
User-agent: anthropic-ai
User-agent: Applebot
User-agent: Applebot-Extended
User-agent: Brightbot 1.0
User-agent: Bytespider
User-agent: CCBot
User-agent: ChatGPT-User
User-agent: Claude-SearchBot
User-agent: Claude-User
User-agent: Claude-Web
User-agent: ClaudeBot
User-agent: cohere-ai
User-agent: cohere-training-data-crawler
User-agent: Cotoyogi
User-agent: Crawlspace
User-agent: Diffbot
User-agent: DuckAssistBot
User-agent: FacebookBot
User-agent: Factset_spyderbot
User-agent: FirecrawlAgent
User-agent: FriendlyCrawler
User-agent: Google-CloudVertexBot
User-agent: Google-Extended
User-agent: GoogleOther
User-agent: GoogleOther-Image
User-agent: GoogleOther-Video
User-agent: GPTBot
User-agent: iaskspider/2.0
User-agent: ICC-Crawler
User-agent: ImagesiftBot
User-agent: img2dataset
User-agent: imgproxy
User-agent: ISSCyberRiskCrawler
User-agent: Kangaroo Bot
User-agent: meta-externalagent
User-agent: Meta-ExternalAgent
User-agent: meta-externalfetcher
User-agent: Meta-ExternalFetcher
User-agent: MistralAI-User/1.0
User-agent: NovaAct
User-agent: OAI-SearchBot
User-agent: omgili
User-agent: omgilibot
User-agent: Operator
User-agent: PanguBot
User-agent: Perplexity-User
User-agent: PerplexityBot
User-agent: PetalBot
User-agent: QualifiedBot
User-agent: Scrapy
User-agent: SemrushBot-OCOB
User-agent: SemrushBot-SWA
User-agent: Sidetrade indexer bot
User-agent: TikTokSpider
User-agent: Timpibot
User-agent: VelenPublicWebCrawler
User-agent: Webzio-Extended
User-agent: wpbot
User-agent: YouBot
Disallow: /

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.nybooks.com/
200https://nybooks.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://nybooks.com/ https://nybooks.com/

Consistent

B
TLS Certificate Expiry & Recommendations
66 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

66
days left
0d 30d 60d 90d+

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • 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 Records
1 A records, 45 ms lookup
PASS
1 A records, 45 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 192.0.66.176
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
5 nameserver(s) configured
Got: ns3.dnsmadeeasy.com, ns0.dnsmadeeasy.com, ns2.dnsmadeeasy.com, ns1.dnsmadeeasy.com, ns4.dnsmadeeasy.com
Info::
1 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 45 ms
Got: 45 ms
A192.0.66.176
AAAA
CNAME
NSns3.dnsmadeeasy.com, ns0.dnsmadeeasy.com, ns2.dnsmadeeasy.com, ns1.dnsmadeeasy.com, ns4.dnsmadeeasy.com
MX
0 nybooks-com.mail.protection.outlook.com
TXT
MS=ms29237962
7gea1it23uf6dslke3rufje0bu
SPF v=spf1 a mx ip4:199.33.226.0/24 ip4:12.15.39.200/29 include:spf.protection.outlo...
google-site-verification=j5eT_lYY9gU40bJzZDbiGLUuPA_Ak-iyxmQZ4Zd-Dpc
google-site-verification=-F_3oVS0SjGgsasQDSyzoTsW2Wz6vYWKb9HyU5lDsgQ
apple-domain-verification=2aG8yMeZIiD9PXyG
fastly-domain-delegation-p9dmgesde4piitar3hof-581394-2023-03-10
ZOOM_verify_tyRtSXBX7pdMTeSb9aiK8Q
facebook-domain-verification=05iqz3nhod4vfcjjun14ll99g9a30z
facebook-domain-verification=d4fpoioj1i85uqjm47zggk01qztyyu
CAALookup not available with standard resolver
Resolved in 45 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
Redirect Chain
1 redirect(s), 803 ms total
PASS
1 redirect(s), 803 ms total
Info::
Single redirect
Got: https://nybooks.com → https://www.nybooks.com/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 803 ms total
Got: 803 ms

https://nybooks.com

5 ms · HTTP/1.1

301

https://www.nybooks.com/

797 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://nybooks.com3015 msHTTP/1.1nginx
2https://www.nybooks.com/200797 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

A+
Domain Intelligence
nybooks.com — via Domain.com - Network Solutions, LLC, 29 years, 11 months old, hosted on WordPress.com (Automattic)
PASS
nybooks.com — via Domain.com - Network Solutions, LLC, 29 years, 11 months old, hosted on WordPress.com (Automattic)
Info::
Domain registered until Feb 1, 2027 (9 months remaining)
Info::
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.
Info::
Registrar: Domain.com - Network Solutions, LLC
Warning::
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.
Info::
Hosting: WordPress.com (Automattic)
Got: AS2635
Domain expiry

230 days

February 1, 2027

SSL certificate

66 days

Issued by Let's Encrypt

Domain age

29 years, 11 months

Registered October 4, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

WordPress.com (Automattic)

ASN AS2635

192.0.66.176

Registrar

Domain.com - Network Solutions, LLC

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Domain.com - Network Solutions, LLC
Created October 4, 1996 (29 years, 11 months ago)
Expires February 1, 2027 (9 months)
Last Updated January 12, 2026
Name Servers ns0.dnsmadeeasy.com, ns1.dnsmadeeasy.com, ns2.dnsmadeeasy.com, ns3.dnsmadeeasy.com
DNSSEC Not enabled
Hosting
IP Address 192.0.66.176
ASN AS2635 (AUTOMATTIC - Automattic, Inc, US)
Provider WordPress.com (Automattic)
Data source: rdap (0.3s)

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 304 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
37 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
0 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
4 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
304 ms
Total Time Total request time from DNS lookup through full response.
305 ms

Connection waterfall

DNS Lookup 37 ms TCP Connect 0 ms TLS Handshake 4 ms Server Processing 263 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.

Send Feedback