Skip to content
https://star-telegram.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 3 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
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

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

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

168
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 OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
1 A records, 41 ms lookup
PASS
1 A records, 41 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 34.85.147.204
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-cloud-b4.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b1.googledomains.com
Info::
5 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: 41 ms
Got: 41 ms
A34.85.147.204
AAAA
CNAME
NSns-cloud-b4.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b1.googledomains.com
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 aspmx2.googlemail.com
10 aspmx3.googlemail.com
TXT
varnish-group=2
SPF v=spf1 include:_spf.mcclatchy.com include:cust-spf.osgbilling.com ip4:54.77.160....
_8qxpx5v772wgizt9s1rr51qtfsyxhbq
ZOOM_verify_tiihFBoPRsCP8e4Fht8oYg
adobe-sign-verification=d42aacceb0cdcd44286532fa2d19780
knowbe4-site-verification=d6e44116a749b1f61f1d7bc9f3e4b677
google-site-verification=eulskXoLTCzr1K31aaLVFAZK2UsE0SF5gQ_iHLZdZf0
adobe-idp-site-verification=23a64011527341e7a0b4471230e84b44977294637c642b8b2348...
tollbit-domain-verification=74a3ce6110fe4b1d67a504b349ec433b36ff3c55c0b1e3afa8ac...
MS=ms50991491 3600
_bu5io9ltlmqu3zjlf2hb9qowhrjlqt9
google-site-verification=5SzWb0TvxNASCFCSJkwr1gqjND0YGqL-HCw2ZgPEpNc
CAALookup not available with standard resolver
Resolved in 41 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
0 redirect(s), 382 ms total
PASS
0 redirect(s), 382 ms total

https://star-telegram.com

382 ms · HTTP/1.0 FINAL

#URLStatusTimeProtocolServer
1https://star-telegram.com301382 msHTTP/1.0BigIP
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

https://www.star-telegram.com/
200https://star-telegram.com/

HTTP → HTTPS

301http://star-telegram.com/ https://www.star-telegram.com/

Consistent

A+
Domain Intelligence
star-telegram.com — via GoDaddy Corporate Domains, LLC, 30 years, 6 months old, hosted on Google Cloud
PASS
star-telegram.com — via GoDaddy Corporate Domains, LLC, 30 years, 6 months old, hosted on Google Cloud
Info::
Domain registered until Mar 21, 2027 (11 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: GoDaddy Corporate Domains, 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: Google Cloud
Got: AS396982
Domain expiry

250 days

March 21, 2027

SSL certificate

168 days

Issued by DigiCert Inc

Domain age

30 years, 6 months

Registered March 20, 1996

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Google Cloud

ASN AS396982

34.85.147.204

Registrar

GoDaddy Corporate Domains, LLC

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar GoDaddy Corporate Domains, LLC
Created March 20, 1996 (30 years, 6 months ago)
Expires March 21, 2027 (11 months)
Last Updated March 12, 2026
Name Servers ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com
DNSSEC Enabled
Hosting
IP Address 34.85.147.204
ASN AS396982 (GOOGLE-CLOUD-PLATFORM - Google LLC, US)
Provider Google Cloud
Data source: rdap (0.3s)

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

Connection waterfall

DNS Lookup 35 ms TCP Connect 95 ms TLS Handshake 193 ms Server Processing 95 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