Skip to content
https://bostonglobe.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
82
GRADE
B
FIX
2
REVIEW
2
PASS
5
INFO
0
Probed from Sao Paulo, Brazil
301 Moved Permanently
Checks
9
5 PASS 2 REVIEW 2 FIX
D
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
FIX
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
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 301 Expected: 301 redirect to HTTPS

www / non-www

200https://www.bostonglobe.com/
200https://bostonglobe.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://bostonglobe.com/ → http://www.bostonglobe.com/

HTTP version does not redirect to HTTPS

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
TLS Certificate Expiry & Recommendations
61 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

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 Records
1 A records, 192 ms lookup
PASS
1 A records, 192 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 198.115.82.77
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: noah.ns.cloudflare.com, teagan.ns.cloudflare.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: 192 ms
Got: 192 ms
A198.115.82.77
AAAA—
CNAME—
NSnoah.ns.cloudflare.com, teagan.ns.cloudflare.com
MX
1 smtp.google.com
TXT
4qk6z66fb7lrxv4n80k317g20wc1b9yj
_bhgs5svdmyxk7rcjq0kz37dzwct5u8m
_globalsign-domain-verification=eRi2ZQZJ99fAou8jrSC06eUJpasrvj8YgWl21vaW5G
_globalsign-domain-verification=xD2Xrm6RMwMJjYQgka9_JIGNgIkA2KVGMdm55GS4H0
_khiro4b2zj724q78o0dyxxvtqz7hvvp
apple-domain-verification=duDOiHNMfMnEqttS
atlassian-domain-verification=vNoVoPJnYrmYhugpzEFYEUUdqZCayYg/xomfDHKFG05C+QSREh...
brave-ledger-verification=c183bc85d6cc5dd16ebfffb74382b43f17ac2d19e7b3e6971039b7...
docusign=549f58fa-181e-458f-b422-8efb90759e60
facebook-domain-verification=wblsmvq0frobdqm0hy836i6kbcmtqu
force push
google-site-verification=0mcPIo29IXxoZUoLSWhuu1pZfw-tSJV2cMR41Ob-HWE
google-site-verification=0tn9a_kR6YN41O5_gwZp8JxpwehE4gaapHsq01YWRn0
google-site-verification=6c0R7056AaKjXoOm4DcW-EJBpviiKKr7-8HLdLHLilw
google-site-verification=8O9_rUQuk19u6W_4xFc6mSM7t13Gher_51AJv8OMCZ8
google-site-verification=C-X2Ydxte5dhmkzynGwJT9D8FSnblQmgagx2Rh_lfOE
google-site-verification=d9oVQAYdM0a75kvQWa_feYfEDgIEh__wv53eYE0w_Oo
google-site-verification=i3Uzu9dgyt7w8leyL9XB1umGJoRv67VE2ogMIwzrSC4
google-site-verification=ngcH2vQsAJqpr-2L5b3K7NRyRsIYbkXCtGUKzUn6RCk
google-site-verification=rzJyVDSaRmaD-6o8wSgTv6KDPjpKElUbQmSKFclffKE
google-site-verification=v1hXnbDOE5QDN2sNkav4RItijj0OGqv_exxXQS7rwlY
openai-domain-verification=dv-yUEkWH8EuXfmOpUBGDCRwoCc
SPF v=spf1 include:_spf.google.com include:mail.zendesk.com include:servers.mcsv.net...
wglf1bxhnfgd7yc2btv48y28rwxxtpgq
CAALookup not available with standard resolver
Resolved in 192 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), 608 ms total
PASS
1 redirect(s), 608 ms total
Info::
Single redirect
Got: https://bostonglobe.com → https://www.bostonglobe.com/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 608 ms total
Got: 608 ms

https://bostonglobe.com

512 ms · HTTP/1.0

301

https://www.bostonglobe.com/

96 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://bostonglobe.com301512 msHTTP/1.0BigIP
2https://www.bostonglobe.com/20096 msHTTP/1.1openresty

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 100 URLs
PASS
robots.txt present, sitemap with 100 URLs
Info::
robots.txt is present
Got: 1095 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 100 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1095 B Sitemaps referenced 3 User-agents ClaudeBot, cohere-training-data-crawler, Diffbot, Google-Extended, Meta-ExternalAgent, Bytespider, FacebookBot, Timpibot, Applebot-Extended, cohere-ai, GPTBot, omgili, Webzio-Extended, AmazonAdBot, AI2Bot, anthropic-ai, CCBot, PanguBot Blocking No — crawling allowed
# Robots.txt for www.bostonglobe.com
# Passionate about publishing and technology? Visit https://www.bostonglobemedia.com/opportunities/

# Sitemaps
Sitemap: https://www.bostonglobe.com/arc/outboundfeeds/news-sitemap/?outputType=xml
Sitemap: https://www.bostonglobe.com/arc/outboundfeeds/sitemap-index-by-day/?outputType=xml
Sitemap: https://www.bostonglobe.com/arc/outboundfeeds/video-sitemap/?outputType=xml

# Allow
User-agent: AmazonAdBot
Allow: /

# AI Bots
User-agent: AI2Bot
Disallow: /

User-agent: anthropic-ai
Disallow: /

User-agent: Applebot-Extended
Disallow: /

User-agent: Bytespider
Disallow: /

User-agent: CCBot
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: cohere-ai
Disallow: /

User-agent: cohere-training-data-crawler
Disallow: /

User-agent: Diffbot
Disallow: /

User-agent: FacebookBot
Disallow: /

User-agent: Google-Extended
Disallow: /

User-agent: GPTBot 
Disallow: /

User-agent: Meta-ExternalAgent
Disallow: /

User-agent: omgili
Disallow: /

User-agent: PanguBot
Disallow: /

User-agent: Timpibot
Disallow: /

User-agent: Webzio-Extended
Disallow: /
sitemap.xml 200 OK
Type URL Set URLs 100 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
bostonglobe.com — via Name106, Inc., 28 years, 8 months old, hosted on BOSTON-GLOBE-NETWORK-01 - Boston Globe Media Partners, LLC, US
PASS
bostonglobe.com — via Name106, Inc., 28 years, 8 months old, hosted on BOSTON-GLOBE-NETWORK-01 - Boston Globe Media Partners, LLC, US
Info::
Domain registered until Jan 13, 2028 (1 years, 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: Name106, Inc.
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: BOSTON-GLOBE-NETWORK-01 - Boston Globe Media Partners, LLC, US
Got: AS11207
Domain expiry

546 days

January 13, 2028

SSL certificate

61 days

Issued by Let's Encrypt

Domain age

28 years, 8 months

Registered January 14, 1998

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

BOSTON-GLOBE-NETWORK-01 - Boston Globe Media Partners, LLC, US

ASN AS11207

198.115.82.77

Registrar

Name106, Inc.

Unlocked 2 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 Name106, Inc.
Created January 14, 1998 (28 years, 8 months ago)
Expires January 13, 2028 (1 years, 9 months)
Last Updated October 2, 2023
Name Servers noah.ns.cloudflare.com, teagan.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 198.115.82.77
ASN AS11207 (BOSTON-GLOBE-NETWORK-01 - Boston Globe Media Partners, LLC, US)
Provider BOSTON-GLOBE-NETWORK-01 - Boston Globe Media Partners, LLC, US
Data source: rdap (0.6s)

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

Connection waterfall

DNS Lookup 5 ms TCP Connect 117 ms TLS Handshake 238 ms Server Processing 118 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