Skip to content
https://katablog.it

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
82
GRADE
B
FIX
1
REVIEW
12
PASS
4
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
17
4 PASS 12 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.

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.
B
Reverse DNS
0/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR for 162.255.161.36 does not match any cert SAN: host.hostrike.com
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
B
Multi-Resolver DNS Speed
Mean 199ms across 3 resolvers (spread 151ms)
REVIEW
Mean 199ms across 3 resolvers (spread 151ms)
Info::
Google: 119ms
Got: 119ms via 8.8.8.8:53
Info::
Cloudflare: 208ms
Got: 208ms via 1.1.1.1:53
Info::
Quad9: 270ms
Got: 270ms via 9.9.9.9:53
B
Redirect Chain
1 redirect(s), 1078 ms total
REVIEW
1 redirect(s), 1078 ms total
Info::
Single redirect
Got: https://katablog.it → https://www.katablog.it/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1078 ms total
Got: 1078 ms

https://katablog.it

759 ms · HTTP/1.1

301

https://www.katablog.it/

319 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://katablog.it301759 msHTTP/1.1Apache
2https://www.katablog.it/200319 msHTTP/1.1Apache

See the visual redirect chain in the HTTP Probe tab →

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.katablog.it/
200https://katablog.it/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://katablog.it/ → https://www.katablog.it/

Consistent

B
HTTP Probe Timing
Total 1071 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
229 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
105 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
108 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.07 s
Total Time Total request time from DNS lookup through full response.
1.07 s

Connection waterfall

DNS Lookup 229 ms TCP Connect 105 ms TLS Handshake 108 ms Server Processing 629 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
86 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

86
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
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
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.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: connection error, /health: connection error, /healthz: connection error, /ping: connection error, /status: connection error.
A
DNS Records
1 A records, 227 ms lookup
PASS
1 A records, 227 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 162.255.161.36
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: ns1.hostrike.com, ns2.hostrike.com
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (227 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 227 ms
A162.255.161.36
AAAA—
CNAME—
NSns1.hostrike.com, ns2.hostrike.com
MX
0 katablog.it
TXT
SPF v=spf1 ip4:184.173.239.120 a mx include:websitewelcome.com ~all
CAALookup not available with standard resolver
Resolved in 227 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

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Crawlability
robots.txt present, sitemap with 4 URLs
PASS
robots.txt present, sitemap with 4 URLs
Info::
robots.txt is present
Got: 173 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 4 entries
Info::
Sitemap index with 4 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 173 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
# START YOAST BLOCK
# ---------------------------
User-agent: *
Disallow:

Sitemap: https://www.katablog.it/sitemap_index.xml
# ---------------------------
# END YOAST BLOCK
sitemap.xml 200 OK
Type Sitemap Index URLs 4 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
katablog.it — via 1API-REG, 14 years, 11 months old, hosted on PRIVATESYSTEMS - PrivateSystems Networks, US
PASS
katablog.it — via 1API-REG, 14 years, 11 months old, hosted on PRIVATESYSTEMS - PrivateSystems Networks, US
Info::
Domain registered until Nov 24, 2026 (3 months remaining)
Info::
Registrar: 1API-REG
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: PRIVATESYSTEMS - PrivateSystems Networks, US
Got: AS63410
Domain expiry

97 days

November 24, 2026

SSL certificate

86 days

Issued by Let's Encrypt

Domain age

14 years, 11 months

Registered November 24, 2011

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

PRIVATESYSTEMS - PrivateSystems Networks, US

ASN AS63410

162.255.161.36

Registrar

1API-REG

Unlocked 2 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 1API-REG
Created November 24, 2011 (14 years, 11 months ago)
Expires November 24, 2026 (3 months)
Last Updated December 10, 2025
Name Servers ns1.hostrike.com, ns2.hostrike.com
Registrant Interactiva
Hosting
IP Address 162.255.161.36
ASN AS63410 (PRIVATESYSTEMS - PrivateSystems Networks, US)
Provider PRIVATESYSTEMS - PrivateSystems Networks, US
Data source: whois (0.8s)

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback