Skip to content
https://informezonal.com.ar

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
92
GRADE
A
FIX
1
REVIEW
7
PASS
9
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
9 PASS 7 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN (document or assets)
FIX
No CDN (document or assets)
Warning::
No CDN (document or assets)
Neither the HTML document nor the page's subresources are served through an edge network. A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN (document or assets)

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).
C
Reverse DNS
Action
0/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
PTR lookup failed for 45.132.157.86: lookup 45.132.157.86: 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 2a02:4780:13:948:0:18c1:ad4f:b: lookup 2a02:4780:13:948:0:18c1:ad4f:b: 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.
C
HTTP Probe Timing
Action
Total 1553 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
100 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
206 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
213 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.28 s
Total Time Total request time from DNS lookup through full response.
1.55 s

Connection waterfall

DNS Lookup 100 ms TCP Connect 206 ms TLS Handshake 213 ms Server Processing 763 ms Content Transfer 271 ms
B
TLS Certificate Expiry & Recommendations
76 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

76
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, 131 ms lookup
PASS
1 A records, 131 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 45.132.157.86
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2a02:4780:13:948:0:18c1:ad4f:b
Info::
2 nameserver(s) configured
Got: byte.dns-parking.com, pixel.dns-parking.com
Info::
2 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 131 ms
Got: 131 ms
A45.132.157.86
AAAA2a02:4780:13:948:0:18c1:ad4f:b
CNAME—
NSbyte.dns-parking.com, pixel.dns-parking.com
MX
5 mx1.hostinger.com
10 mx2.hostinger.com
TXT
SPF v=spf1 include:_spf.mail.hostinger.com ~all
CAALookup not available with standard resolver
Resolved in 131 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

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A
CAA Records
issue: pki.goog, comodoca.com, globalsign.com, digicert.com, sectigo.com, letsencrypt.org | issuewild: letsencrypt.org, pki.goog, sectigo.com, globalsign.com, comodoca.com, digicert.com
PASS
issue: pki.goog, comodoca.com, globalsign.com, digicert.com, sectigo.com, letsencrypt.org | issuewild: letsencrypt.org, pki.goog, sectigo.com, globalsign.com, comodoca.com, digicert.com
Info::
CAA issue tag present — authorized CA(s): pki.goog, comodoca.com, globalsign.com, digicert.com, sectigo.com, letsencrypt.org
Info::
No CAA iodef tag — won't be notified of failed issuance attempts
Add `0 iodef "mailto:security@example.com"` to receive notifications when a CA refuses issuance because it doesn't match your CAA policy. Useful signal for detecting issuance attempts by unauthorized CAs.
A
Multi-Resolver DNS Speed
Mean 75ms across 3 resolvers (spread 75ms)
PASS
Mean 75ms across 3 resolvers (spread 75ms)
Info::
Cloudflare: 50ms
Got: 50ms via 1.1.1.1:53
Info::
Google: 51ms
Got: 51ms via 8.8.8.8:53
Info::
Quad9: 125ms
Got: 125ms 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://informezonal.com.ar

https://informezonal.com.ar

1431 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://informezonal.com.ar2001431 msHTTP/1.1LiteSpeed
A+
IPv6 Readiness
IPv6 reachable (204 ms)
PASS
IPv6 reachable (204 ms)
Info::
IPv6 is configured and reachable at 2a02:4780:13:948:0:18c1:ad4f:b
Got: 204 ms connect
IPv6 Ready
AAAA Records 2a02:4780:13:948:0:18c1:ad4f:b Connection Reachable (204 ms)
A+
Crawlability
robots.txt present, sitemap with 7 URLs
PASS
robots.txt present, sitemap with 7 URLs
Info::
robots.txt is present
Got: 120 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 7 entries
Info::
Sitemap index with 7 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 120 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php

Sitemap: https://informezonal.com.ar/wp-sitemap.xml

A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

https://www.informezonal.com.ar/
200https://informezonal.com.ar/

HTTP → HTTPS

301http://informezonal.com.ar/ → https://informezonal.com.ar/

Consistent

A+
Domain Intelligence
informezonal.com.ar — via nicar, 10 years, 5 months old
PASS
informezonal.com.ar — via nicar, 10 years, 5 months old
Info::
Domain registered until Aug 14, 2027 (9 months remaining)
Info::
Registrar: nicar
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

296 days

August 14, 2027

SSL certificate

76 days

Issued by Let's Encrypt

Domain age

10 years, 5 months

Registered July 14, 2016

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

2a02:4780:13:948:0:18c1:ad4f:b

Registrar

nicar

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 nicar
Created July 14, 2016 (10 years, 5 months ago)
Expires August 14, 2027 (9 months)
Last Updated August 6, 2025
Name Servers byte.dns-parking.com, pixel.dns-parking.com
Hosting
IP Address 2a02:4780:13:948:0:18c1:ad4f:b
Data source: rdap (1.2s)

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