Skip to content
https://chronicle.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
GRADE
B
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from New York, United Stated
301 Moved Permanently
Checks
9
6 PASS 3 REVIEW
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
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.chronicle.com/
200https://chronicle.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://chronicle.com/ https://www.chronicle.com/

Consistent

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

Certificate validity

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

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
A+
DNS Records
4 A records, 107 ms lookup
PASS
4 A records, 107 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 99.84.160.38, 99.84.160.51, 99.84.160.39, 99.84.160.73
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1045.awsdns-02.org, ns-140.awsdns-17.com, ns-1997.awsdns-57.co.uk, ns-817.awsdns-38.net
Info::
3 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: 107 ms
Got: 107 ms
A99.84.160.38, 99.84.160.51, 99.84.160.39, 99.84.160.73
AAAA
CNAME
NSns-1045.awsdns-02.org, ns-140.awsdns-17.com, ns-1997.awsdns-57.co.uk, ns-817.awsdns-38.net
MX
0 mxb-008c5001.gslb.pphosted.com
0 mxa-008c5001.gslb.pphosted.com
32767 ms69735204.msv1.invalid
TXT
ZOOM_verify_hoCYRVTuQQXOotdMVCVWsx
_globalsign-domain-verification=Dqd8I0hWasEjsEu2h5gF7evwjvRwfcjM-jfbkxfhb-
adobe-idp-site-verification=3380a292c5fe92c10b4bb843f70c593f5149d40060a2b049e944...
d2sg0aymvy0li1.cloudfront.net
facebook-domain-verification=5v4h15h1mtrkdbw27xfkld161mllwf
globalsign-domain-verification=2f87c0c7172380296838e8ef63e87230
globalsign-domain-verification=3699a4ef96609176f46cef43837026f4
google-site-verification=ghHJlxYD0vKv90DHLyYMvjwNw3N71lfB8Je5KWITGNA
google-site-verification=ydfkHmEE4bq_pfx6_0wsxAdmetG8VpL2XkZbLCV1gX0
openai-domain-verification=dv-UuAcQejjXeQjTt0J8xqa5Vr5
slack-domain-verification=cPqGwGQvXliSCN0WXKB0T7c5XIp4jUmsetX1uf9f
SPF v=spf1 ip4:192.91.251.26 ip4:34.236.219.51 ip4:52.0.131.254 ip4:54.156.195.156 i...
CAALookup not available with standard resolver
Resolved in 107 ms

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), 79 ms total
PASS
1 redirect(s), 79 ms total
Info::
Single redirect
Got: https://chronicle.com → https://www.chronicle.com/ (301)
Info::
WWW normalization redirect

https://chronicle.com

19 ms · HTTP/1.1

301

https://www.chronicle.com/

60 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://chronicle.com30119 msHTTP/1.1AmazonS3
2https://www.chronicle.com/20060 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 488 URLs
PASS
robots.txt present, sitemap with 488 URLs
Info::
robots.txt is present
Got: 1810 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 488 entries
Info::
Sitemap index with 488 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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 1810 B Sitemaps referenced 0 User-agents meta-externalagent, *, ClaudeBot, CloudflareBrowserRenderingCrawler, GPTBot, Amazonbot, Applebot-Extended, Bytespider, CCBot, Google-Extended Blocking No — crawling allowed
# As a condition of accessing this website, you agree to abide by the following
# content signals:

# (a)  If a Content-Signal = yes, you may collect content for the corresponding
#      use.
# (b)  If a Content-Signal = no, you may not collect content for the
#      corresponding use.
# (c)  If the website operator does not include a Content-Signal for a
#      corresponding use, the website operator neither grants nor restricts
#      permission via Content-Signal with respect to the corresponding use.

# The content signals and their meanings are:

# search:   building a search index and providing search results (e.g., returning
#           hyperlinks and short excerpts from your website's contents). Search does not
#           include providing AI-generated search summaries.
# ai-input: inputting content into one or more AI models (e.g., retrieval
#           augmented generation, grounding, or other real-time taking of content for
#           generative AI search answers).
# ai-train: training or fine-tuning AI models.

# ANY RESTRICTIONS EXPRESSED VIA CONTENT SIGNALS ARE EXPRESS RESERVATIONS OF
# RIGHTS UNDER ARTICLE 4 OF THE EUROPEAN UNION DIRECTIVE 2019/790 ON COPYRIGHT
# AND RELATED RIGHTS IN THE DIGITAL SINGLE MARKET.

# BEGIN Cloudflare Managed content

User-agent: *
Content-Signal: search=yes,ai-train=no
Allow: /

User-agent: Amazonbot
Disallow: /

User-agent: Applebot-Extended
Disallow: /

User-agent: Bytespider
Disallow: /

User-agent: CCBot
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: CloudflareBrowserRenderingCrawler
Disallow: /

User-agent: Google-Extended
Disallow: /

User-agent: GPTBot
Disallow: /

User-agent: meta-externalagent
Disallow: /

# END Cloudflare Managed Content

User-agent: *
Crawl-delay: 10
Disallow: /account/login
Disallow: /search
sitemap.xml 200 OK
Type Sitemap Index URLs 488 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
chronicle.com — via Network Solutions, LLC, 32 years, 3 months old, hosted on AWS
PASS
chronicle.com — via Network Solutions, LLC, 32 years, 3 months old, hosted on AWS
Info::
Domain registered until Jun 14, 2028 (2 years, 2 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: 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: AWS
Got: AS16509
Domain expiry

697 days

June 14, 2028

SSL certificate

128 days

Issued by Amazon

Domain age

32 years, 3 months

Registered June 15, 1994

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

3.162.112.99

Registrar

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 Network Solutions, LLC
Created June 15, 1994 (32 years, 3 months ago)
Expires June 14, 2028 (2 years, 2 months)
Last Updated April 15, 2026
Name Servers ns-1045.awsdns-02.org, ns-140.awsdns-17.com, ns-1997.awsdns-57.co.uk, ns-817.awsdns-38.net
DNSSEC Not enabled
Hosting
IP Address 3.162.112.99
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.1s)

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 19 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
11 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 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.
20 ms
Total Time Total request time from DNS lookup through full response.
20 ms

Connection waterfall

DNS Lookup 11 ms TCP Connect 1 ms TLS Handshake 4 ms Server Processing 3 ms Content Transfer 0 ms
A+
CDN & Delivery
AWS CloudFront (Hit from cloudfront)
PASS
AWS CloudFront (Hit from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: JFK50-P15)
Got: x-amz-cf-id: aUtlitEB16mOfd57nqFVbBYySzvHm-yqEo03dmAxAGqpvVUwiDB11Q==
Info::
CDN cache status: Hit from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status Hit from cloudfront Evidence x-amz-cf-id: aUtlitEB16mOfd57nqFVbBYySzvHm-yqEo03dmAxAGqpvVUwiDB11Q==
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback