Skip to content
https://vanelia.shop

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
1
REVIEW
8
PASS
7
INFO
1
Probed from Madrid, Spain
200 OK
Checks
17
7 PASS 8 REVIEW 1 FIX
D
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
FIX
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
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 200 Expected: 301 redirect to HTTPS

www / non-www

200https://www.vanelia.shop/
200https://vanelia.shop/

Inconsistent — duplicate content risk

HTTP → HTTPS

200http://vanelia.shop/

HTTP version does not redirect to HTTPS

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 188.114.96.2: lookup 188.114.96.2: 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 188.114.97.2: lookup 188.114.97.2: 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 2a06:98c1:3121::2: lookup 2a06:98c1:3121::2: 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 2a06:98c1:3120::2: lookup 2a06:98c1:3120::2: 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
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 26 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your 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

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 26 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *

Disallow:
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
HTTP Probe Timing
Total 1244 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
54 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.
31 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.15 s
Total Time Total request time from DNS lookup through full response.
1.24 s

Connection waterfall

DNS Lookup 54 ms TCP Connect 17 ms TLS Handshake 31 ms Server Processing 1.05 s Content Transfer 90 ms
B
TLS Certificate Expiry & Recommendations
72 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

72
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: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A+
DNS Records
2 A records, 49 ms lookup
PASS
2 A records, 49 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 188.114.96.2, 188.114.97.2
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2a06:98c1:3121::2, 2a06:98c1:3120::2
Info::
2 nameserver(s) configured
Got: uriah.ns.cloudflare.com, ingrid.ns.cloudflare.com
Info::
3 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 49 ms
Got: 49 ms
A188.114.96.2, 188.114.97.2
AAAA2a06:98c1:3121::2, 2a06:98c1:3120::2
CNAME—
NSuriah.ns.cloudflare.com, ingrid.ns.cloudflare.com
MX
5 mx1-hosting.jellyfish.systems
10 mx2-hosting.jellyfish.systems
20 mx3-hosting.jellyfish.systems
TXT
google-site-verification=3-65Q82atcP6zQygXTKOxN-l4CAjkehYioR_24xFedg
SPF v=spf1 +a +mx +ip4:66.29.137.70 include:spf.web-hosting.com ~all
CAALookup not available with standard resolver
Resolved in 49 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 19ms across 3 resolvers (spread 29ms)
PASS
Mean 19ms across 3 resolvers (spread 29ms)
Info::
Quad9: 6ms
Got: 6ms via 9.9.9.9:53
Info::
Cloudflare: 18ms
Got: 18ms via 1.1.1.1:53
Info::
Google: 35ms
Got: 35ms via 8.8.8.8:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://vanelia.shop

https://vanelia.shop

1058 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://vanelia.shop2001058 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2a06:98c1:3121::2, 2a06:98c1:3120::2
Got: 17 ms connect
IPv6 Ready
AAAA Records 2a06:98c1:3121::2, 2a06:98c1:3120::2 Connection Reachable (17 ms)
A
CDN & Delivery
Document and assets on Cloudflare
PASS
Document and assets on Cloudflare
Info::
Document is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: a555f702df6cebb2-CDG
Info::
CDN cache status: DYNAMIC
Info::
Assets on Cloudflare: cdnjs.cloudflare.com (assets: 3), cache HIT
Got: cf-ray: a555f9a3d9da8e67-CDG
Document served via CDN: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: a555f702df6cebb2-CDG

Asset hosts on a CDN

  • cdnjs.cloudflare.com — Cloudflare · assets: 3 · Cache Status: HIT

Other asset hosts

  • cdn.jsdelivr.net — assets: 2 · below probe threshold
  • connect.facebook.net — assets: 2 · below probe threshold
  • www.googletagmanager.com — assets: 1 · below probe threshold
A+
CDN Cache Observability
Cache state: DYNAMIC
PASS
Cache state: DYNAMIC
Info::
CDN cache state observable via 1 header(s)
Got: cf-cache-status=DYNAMIC
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