Skip to content
https://espiralturismoinductivo.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
1
REVIEW
9
PASS
7
INFO
0
Probed from Santa Clara, United States
200 OK
Checks
17
7 PASS 9 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).
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 82.98.164.82 does not match any cert SAN: hl1637.dinaserver.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 155ms across 3 resolvers (spread 21ms)
REVIEW
Mean 155ms across 3 resolvers (spread 21ms)
Info::
Cloudflare: 146ms
Got: 146ms via 1.1.1.1:53
Info::
Google: 153ms
Got: 153ms via 8.8.8.8:53
Info::
Quad9: 167ms
Got: 167ms via 9.9.9.9:53
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
HTTP Probe Timing
Total 1313 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
687 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
155 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
158 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.31 s
Total Time Total request time from DNS lookup through full response.
1.31 s

Connection waterfall

DNS Lookup 687 ms TCP Connect 155 ms TLS Handshake 158 ms Server Processing 311 ms Content Transfer 1 ms
B
TLS Certificate Expiry & Recommendations
68 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

68
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.
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: 429, /health: 429, /healthz: 429, /ping: 404, /status: 429.
A
DNS Records
1 A records, 427 ms lookup
PASS
1 A records, 427 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 82.98.164.82
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: ns4.dinahosting.com, ns.dinahosting.com, ns3.dinahosting.com, ns2.dinahosting.com
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (427 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 427 ms
A82.98.164.82
AAAA—
CNAME—
NSns4.dinahosting.com, ns.dinahosting.com, ns3.dinahosting.com, ns2.dinahosting.com
MX
10 mail.espiralturismoinductivo.com
TXT
SPF v=spf1 a mx ~all
CAALookup not available with standard resolver
Resolved in 427 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+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://espiralturismoinductivo.com

https://espiralturismoinductivo.com

855 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://espiralturismoinductivo.com200855 msHTTP/1.1HTTPd
A+
Crawlability
robots.txt present, sitemap with 3 URLs
PASS
robots.txt present, sitemap with 3 URLs
Info::
robots.txt is present
Got: 131 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 3 entries
Info::
Sitemap index with 3 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 131 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php

Sitemap: https://espiralturismoinductivo.com/sitemap_index.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 3 entries Valid XML Yes
Child Sitemaps:
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

429https://www.espiralturismoinductivo.com/
200https://espiralturismoinductivo.com/

HTTP → HTTPS

301http://espiralturismoinductivo.com/ → https://espiralturismoinductivo.com/

Consistent

A+
Domain Intelligence
espiralturismoinductivo.com — via Dinahosting s.l., 1 months old, hosted on DINAHOSTING-AS - DinaHosting S.L., ES
PASS
espiralturismoinductivo.com — via Dinahosting s.l., 1 months old, hosted on DINAHOSTING-AS - DinaHosting S.L., ES
Info::
Domain registered until Aug 7, 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 Aug 7, 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: Dinahosting s.l.
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: DINAHOSTING-AS - DinaHosting S.L., ES
Got: AS42612
Domain expiry

313 days

August 7, 2027

SSL certificate

68 days

Issued by Let's Encrypt

Domain age

1 months

Registered August 7, 2026

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

DINAHOSTING-AS - DinaHosting S.L., ES

ASN AS42612

82.98.164.82

Registrar

Dinahosting s.l.

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
  • Newly registered domain — build backlinks and content to establish SEO trust
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Dinahosting s.l.
Created August 7, 2026 (1 months ago)
Expires August 7, 2027 (10 months)
Last Updated August 7, 2026
Name Servers ns.dinahosting.com, ns2.dinahosting.com, ns3.dinahosting.com, ns4.dinahosting.com
DNSSEC Not enabled
Hosting
IP Address 82.98.164.82
ASN AS42612 (DINAHOSTING-AS - DinaHosting S.L., ES)
Provider DINAHOSTING-AS - DinaHosting S.L., ES
Data source: rdap (0.3s)

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+
CDN Cache Observability
Cache state: Age=795s
PASS
Cache state: Age=795s
Info::
CDN cache state observable via 1 header(s)
Got: age=795
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback