Skip to content
https://thebalkanchronicle.com/en/

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
92
GRADE
A
FIX
0
REVIEW
5
PASS
12
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
12 PASS 5 REVIEW
B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
C
Reverse DNS
Action
0/4 IPs match cert SAN
REVIEW
0/4 IPs match cert SAN
Info::
PTR lookup failed for 172.67.133.5: lookup 172.67.133.5: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 104.21.5.58: lookup 104.21.5.58: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2606:4700:3037::ac43:8505: lookup 2606:4700:3037::ac43:8505: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2606:4700:3031::6815:53a: lookup 2606:4700:3031::6815:53a: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
B
TLS Certificate Expiry & Recommendations
85 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

85
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
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
A+
DNS Records
2 A records, 38 ms lookup
PASS
2 A records, 38 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 172.67.133.5, 104.21.5.58
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:3037::ac43:8505, 2606:4700:3031::6815:53a
Info::
2 nameserver(s) configured
Got: alice.ns.cloudflare.com, kolton.ns.cloudflare.com
Info::
3 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 38 ms
Got: 38 ms
A172.67.133.5, 104.21.5.58
AAAA2606:4700:3037::ac43:8505, 2606:4700:3031::6815:53a
CNAME—
NSalice.ns.cloudflare.com, kolton.ns.cloudflare.com
MX
7 route2.mx.cloudflare.net
40 route3.mx.cloudflare.net
46 route1.mx.cloudflare.net
TXT
google-site-verification=cK1fkZLUoUztafWzktFKsjPNHMPTTQ_4aHJBlc9qCBk
SPF v=spf1 include:_spf.mx.cloudflare.net ~all
CAALookup not available with standard resolver
Resolved in 38 ms
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Multi-Resolver DNS Speed
Mean 40ms across 3 resolvers (spread 25ms)
PASS
Mean 40ms across 3 resolvers (spread 25ms)
Info::
Cloudflare: 28ms
Got: 28ms via 1.1.1.1:53
Info::
Google: 39ms
Got: 39ms via 8.8.8.8:53
Info::
Quad9: 53ms
Got: 53ms via 9.9.9.9:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://thebalkanchronicle.com/en/

https://thebalkanchronicle.com/en/

100 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://thebalkanchronicle.com/en/200100 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (16 ms)
PASS
IPv6 reachable (16 ms)
Info::
IPv6 is configured and reachable at 2606:4700:3037::ac43:8505, 2606:4700:3031::6815:53a
Got: 16 ms connect
IPv6 Ready
AAAA Records 2606:4700:3037::ac43:8505, 2606:4700:3031::6815:53a Connection Reachable (16 ms)
A+
Crawlability
robots.txt present, sitemap with 271 URLs
PASS
robots.txt present, sitemap with 271 URLs
Info::
robots.txt is present
Got: 759 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 271 entries
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 759 B Sitemaps referenced 0 User-agents Blocking No — crawling allowed
<!doctype html><title>Redirecting to: https://thebalkanchronicle.com/es</title><meta http-equiv="refresh" content="2;url=https://thebalkanchronicle.com/es"><meta name="robots" content="noindex"><link rel="canonical" href="https://thebalkanchronicle.com/es"><body>	<a href="https://thebalkanchronicle.com/es">Redirecting from <code>/</code> to <code>https://thebalkanchronicle.com/es</code></a><script type="module" src="https://static.cloudflareinsights.com/beacon.min.js/v4513226cdae34746b4dedf0b4dfa099e1781791509496" integrity="sha512-ZE9pZaUXND66v380QUtch/5sE9tPFh2zg45pR2PB0CVkCtOREv2AJKkSidISWkysEuQ0EH8faUU5du78bx87UQ==" data-cf-beacon='{"version":"2024.11.0","token":"8937f2af7514493ab6d5b4568200c6e3","r":1}' crossorigin="anonymous"></script>
</body>
sitemap.xml 200 OK
Type URL Set URLs 271 entries Valid XML Yes
Sample URLs:
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.thebalkanchronicle.com/en/
200https://thebalkanchronicle.com/en/

Trailing Slash

200https://thebalkanchronicle.com/en/
308https://thebalkanchronicle.com/en

HTTP → HTTPS

301http://thebalkanchronicle.com/en/ → https://thebalkanchronicle.com/en/

Consistent

A+
Domain Intelligence
thebalkanchronicle.com — via Cloudflare, Inc., 1 months old
PASS
thebalkanchronicle.com — via Cloudflare, Inc., 1 months old
Info::
Domain registered until Jun 4, 2027 (10 months remaining)
Info::
Domain is only 1 months old
Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.
Got: Registered Jun 4, 2026
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: Cloudflare, 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.
Domain expiry

313 days

June 4, 2027

SSL certificate

85 days

Issued by Google Trust Services

Domain age

1 months

Registered June 4, 2026

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:3037::ac43:8505

Registrar

Cloudflare, 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
  • Newly registered domain — build backlinks and content to establish SEO trust
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Cloudflare, Inc.
Created June 4, 2026 (1 months ago)
Expires June 4, 2027 (10 months)
Last Updated June 4, 2026
Name Servers alice.ns.cloudflare.com, kolton.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700:3037::ac43:8505
Data source: rdap (0.2s)

Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.

Why this matters

Informational: domain age. Newer domains may have lower trust signals in spam/security filters.

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

Connection waterfall

DNS Lookup 39 ms TCP Connect 21 ms TLS Handshake 25 ms Server Processing 65 ms Content Transfer 1 ms
A
CDN & Delivery
Cloudflare (DYNAMIC)
PASS
Cloudflare (DYNAMIC)
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: a20b1d569998ca0e-CDG
Info::
CDN cache status: DYNAMIC
CDN Detected: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: a20b1d569998ca0e-CDG
A+
CDN Cache Observability
Cache state: DYNAMIC
PASS
Cache state: DYNAMIC
Info::
CDN cache state observable via 1 header(s)
Got: cf-cache-status=DYNAMIC
A+
Health Check Endpoint
Health endpoint at https://thebalkanchronicle.com/health (HTTP 200)
PASS
Health endpoint at https://thebalkanchronicle.com/health (HTTP 200)
Info::
Public health endpoint at https://thebalkanchronicle.com/health
Got: https://thebalkanchronicle.com/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback