Skip to content
https://enjoycbd.es

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
67
GRADE
D
FIX
3
REVIEW
10
PASS
3
INFO
1
Probed from Singapore, Singapore
307 Temporary Redirect
Checks
17
3 PASS 10 REVIEW 3 FIX
F
Multi-Resolver DNS Speed
Action
All public resolvers failed to resolve the domain
FIX
All public resolvers failed to resolve the domain
Critical::
DNS resolution failed against all public resolvers
1.1.1.1, 8.8.8.8, and 9.9.9.9 all failed to resolve this domain. Almost always means the domain is delegated incorrectly, the authoritative servers are unreachable, or the resolution returned NXDOMAIN/SERVFAIL across the board.
F
HTTP Probe Timing
Action
Total 6065 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
FIX
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
466 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
242 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
245 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
6.07 s
Total Time Total request time from DNS lookup through full response.
6.07 s

Connection waterfall

DNS Lookup 466 ms TCP Connect 242 ms TLS Handshake 245 ms Server Processing 5.11 s Content Transfer 0 ms
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.

C
DNSSEC
Action
DNSSEC posture not checked
REVIEW
DNSSEC posture not checked
Info::
DNSSEC posture not checked
Could not query the validating resolver for DNSSEC status. Network or resolver outage.
C
CAA Records
Action
CAA posture not checked
REVIEW
CAA posture not checked
Info::
CAA records not checked
Could not query the resolver for CAA records. Network or resolver outage.
B
Reverse DNS
0/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR for 204.93.224.158 does not match any cert SAN: bh8964.banahosting.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
Redirect Chain
1 redirect(s), 2133 ms total
REVIEW
1 redirect(s), 2133 ms total
Info::
Single redirect
Got: https://enjoycbd.es → https://enjoycbd.es/?v=90610593aedc (307)
Warning::
Redirect overhead: 2133 ms total
Got: 2133 ms

https://enjoycbd.es

1891 ms · HTTP/1.1

307

https://enjoycbd.es/?v=90610593aedc

242 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://enjoycbd.es3071891 msHTTP/1.1
2https://enjoycbd.es/?v=90610593aedc200242 msHTTP/1.1

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::
HTTP version does not redirect to HTTPS
Got: HTTP 0 Expected: 301 redirect to HTTPS

www / non-www

https://www.enjoycbd.es/
200https://enjoycbd.es/

HTTP → HTTPS

http://enjoycbd.es/

HTTP version does not redirect to HTTPS

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

Certificate validity

54
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, 467 ms lookup
PASS
1 A records, 467 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 204.93.224.158
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: ns8965.banahosting.com, ns8964.banahosting.com
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (467 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 467 ms
A204.93.224.158
AAAA—
CNAME—
NSns8965.banahosting.com, ns8964.banahosting.com
MX
0 enjoycbd.es
TXT
SPF v=spf1 +a +mx include:relay.mailchannels.net ~all
CAALookup not available with standard resolver
Resolved in 467 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, no sitemap
PASS
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 439 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt references sitemap

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more ▾

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

robots.txt 200 OK
Size 439 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /wp-content/uploads/wc-logs/
Disallow: /wp-content/uploads/woocommerce_transient_files/
Disallow: /wp-content/uploads/woocommerce_uploads/
Disallow: /*?add-to-cart=
Disallow: /*?*add-to-cart=
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php

# START YOAST BLOCK
# ---------------------------
User-agent: *
Disallow:

Sitemap: https://enjoycbd.es/sitemap_index.xml
# ---------------------------
# END YOAST BLOCK
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

Domain Intelligence
Domain intelligence data not available
INFO
Domain intelligence data not available

RDAP and WHOIS lookup both failed

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

Send Feedback