Skip to content
https://ecuadorvisas.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
0
REVIEW
7
PASS
10
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
10 PASS 7 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 104.21.77.56: lookup 104.21.77.56: 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 172.67.204.214: lookup 172.67.204.214: 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:3035::ac43:ccd6: lookup 2606:4700:3035::ac43:ccd6: 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::6815:4d38: lookup 2606:4700:3037::6815:4d38: 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
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 redirects to HTTPS permanently
Got: HTTP 301

www / non-www

200https://www.ecuadorvisas.com/
200https://ecuadorvisas.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

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

Certificate validity

48
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: 410, /health: 410, /healthz: 410, /ping: 410, /status: 410.
A+
DNS Records
2 A records, 135 ms lookup
PASS
2 A records, 135 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.21.77.56, 172.67.204.214
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:3035::ac43:ccd6, 2606:4700:3037::6815:4d38
Info::
2 nameserver(s) configured
Got: clark.ns.cloudflare.com, asa.ns.cloudflare.com
Info::
6 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 135 ms
Got: 135 ms
A104.21.77.56, 172.67.204.214
AAAA2606:4700:3035::ac43:ccd6, 2606:4700:3037::6815:4d38
CNAME—
NSclark.ns.cloudflare.com, asa.ns.cloudflare.com
MX
1 ASPMX.L.GOOGLE.com
5 ALT1.ASPMX.L.GOOGLE.com
5 ALT2.ASPMX.L.GOOGLE.com
10 ALT3.ASPMX.L.GOOGLE.com
10 ALT4.ASPMX.L.GOOGLE.com
25 mx1.mailchannels.net
TXT
google-site-verification=P4fBo8uSWf69gdOuPg0-qxP2vHnUa46El2Lz3iha3UA
SPF v=spf1 include:_spf.google.com ~all
google-site-verification=3R-et5npX1ZvvGk16t9PjNURwJRENyXCqw66N50-CmM
CAALookup not available with standard resolver
Resolved in 135 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 36ms across 3 resolvers (spread 17ms)
PASS
Mean 36ms across 3 resolvers (spread 17ms)
Info::
Google: 29ms
Got: 29ms via 8.8.8.8:53
Info::
Quad9: 34ms
Got: 34ms via 9.9.9.9:53
Info::
Cloudflare: 46ms
Got: 46ms via 1.1.1.1:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://ecuadorvisas.com

https://ecuadorvisas.com

141 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://ecuadorvisas.com200141 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700:3035::ac43:ccd6, 2606:4700:3037::6815:4d38
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700:3035::ac43:ccd6, 2606:4700:3037::6815:4d38 Connection Reachable (17 ms)
A+
Crawlability
robots.txt present, sitemap with 68 URLs
PASS
robots.txt present, sitemap with 68 URLs
Info::
robots.txt is present
Got: 2065 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 68 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 2065 B Sitemaps referenced 0 User-agents ChatGPT-User, Kimi-User, Amzn-User, Instapaper, ChathiveCrawler, *, Claude-User, Google-Agent, Google-NotebookLM, meta-externalfetcher, Perplexity-User, FireCrawl, FirecrawlAgent, MistralAI-User, Retool, Google-GeminiNotebook 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.
# use:      how AI systems may consume the content (immediate, reference, or full).

# 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=yes,use=reference
Allow: /

# AI Agents
User-agent: Perplexity-User
Disallow: /

User-agent: FireCrawl
Disallow: /

User-agent: FirecrawlAgent
Disallow: /

User-agent: Claude-User
Disallow: /

User-agent: ChatGPT-User
Disallow: /

User-agent: Google-Agent
Disallow: /

User-agent: Google-GeminiNotebook
User-agent: Google-NotebookLM
Disallow: /

User-agent: MistralAI-User
Disallow: /

User-agent: Kimi-User
Disallow: /

User-agent: Amzn-User
Disallow: /

User-agent: meta-externalfetcher
Disallow: /

User-agent: Retool
Disallow: /

User-agent: Instapaper
Disallow: /

User-agent: ChathiveCrawler
Disallow: /

# END Cloudflare Managed Content
sitemap.xml 200 OK
Type URL Set URLs 68 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
ecuadorvisas.com — via Cloudflare, Inc., 13 years, 3 months old
PASS
ecuadorvisas.com — via Cloudflare, Inc., 13 years, 3 months old
Info::
Domain registered until Oct 11, 2027 (11 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: 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

335 days

October 11, 2027

SSL certificate

48 days

Issued by Let's Encrypt

Domain age

13 years, 3 months

Registered October 11, 2013

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:3037::6815:4d38

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
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Cloudflare, Inc.
Created October 11, 2013 (13 years, 3 months ago)
Expires October 11, 2027 (11 months)
Last Updated October 5, 2026
Name Servers asa.ns.cloudflare.com, clark.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700:3037::6815:4d38
Data source: rdap (0.2s)

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

Connection waterfall

DNS Lookup 40 ms TCP Connect 17 ms TLS Handshake 25 ms Server Processing 243 ms Content Transfer 1 ms
A+
CDN & Delivery
Cloudflare (HIT)
PASS
Cloudflare (HIT)
Info::
Document is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: a57f840acea37ae7-CDG
Info::
CDN cache status: HIT
Document served via CDN: Cloudflare
Provider Cloudflare Cache Status HIT Evidence cf-ray: a57f840acea37ae7-CDG
A+
CDN Cache Observability
Cache state: HIT
PASS
Cache state: HIT
Info::
CDN cache state observable via 1 header(s)
Got: cf-cache-status=HIT
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback