Skip to content
https://puravidabracelets.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from Amsterdam, Netherlands
429 Too Many Requests
Checks
9
5 PASS 4 REVIEW
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
Crawlability
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

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 No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

82
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 & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: AMS)
Got: cf-ray: 9e8fd1a288a53441-AMS
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9e8fd1a288a53441-AMS
A+
DNS Records
1 A records, 25 ms lookup
PASS
1 A records, 25 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 23.227.38.32
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: ns41.domaincontrol.com, ns42.domaincontrol.com, ns51.domaincontrol.com, ns52.domaincontrol.com
Info::
1 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 25 ms
Got: 25 ms
A23.227.38.32
AAAA
CNAME
NSns41.domaincontrol.com, ns42.domaincontrol.com, ns51.domaincontrol.com, ns52.domaincontrol.com
MX
0 puravidabracelets-com.mail.protection.outlook.com
TXT
SPF v=spf1 include:spf.protection.outlook.com include:email.rechargeapps.com -all
facebook-domain-verification=5bdcl98kb7qht1nuehqpkghcjibd80
google-site-verification=NSrV25eZ7ybqpLWzJiPSpFUs2LNhV4O8vwMIVwLN1OI
MS=ms40483682
google-site-verification=Nt4-X1yV3F9C4IfyxVbLpbfd9I33-0LDxqWVxpzcHdQ
atlassian-domain-verification=UCfnezkqHK0nqfYVTjUbNL/WjRjh7lvHOhZ94i9EEnpPn3iDS6...
MS=5728076C31076E4123D516838B27013620A7A23C
nintex.61ae329ee8f0c201ab95c77b
miro-verification=4140c164fd7a8a8fda3f5503f06dc90fd051f3b2
nintex.65aa944f358dd32c798d83f3
knowbe4-site-verification=365eb720ee8aaba60f81fa49669cf809
google-site-verification=UNQ7nqXC_lBJ8gOWmp0Jhs4qdO4kY4bVJmpSqkYlDBI
google-site-verification=0PmYhTOIj34yu5uUSFGWVN6C3o5ll6rWt64GT19f4mE
SPF v=spf1 include:amazonses.com ~all
CAALookup not available with standard resolver
Resolved in 25 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

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A+
Redirect Chain
0 redirect(s), 35 ms total
PASS
0 redirect(s), 35 ms total

https://puravidabracelets.com

35 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://puravidabracelets.com42935 msHTTP/1.1cloudflare
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

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

HTTP → HTTPS

301http://puravidabracelets.com/ https://puravidabracelets.com/

Consistent

A+
Domain Intelligence
puravidabracelets.com — via GoDaddy.com, LLC, 15 years, 11 months old, hosted on Cloudflare
PASS
puravidabracelets.com — via GoDaddy.com, LLC, 15 years, 11 months old, hosted on Cloudflare
Info::
Domain registered until Jul 9, 2026 (3 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: GoDaddy.com, LLC
Info::
Hosting: Cloudflare
Got: AS13335
Domain expiry

43 days

July 9, 2026

SSL certificate

82 days

Issued by Let's Encrypt

Domain age

15 years, 11 months

Registered July 9, 2010

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

23.227.38.32

Registrar

GoDaddy.com, LLC

Lock status unknown 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable DNSSEC to protect visitors from DNS spoofing
Registrar GoDaddy.com, LLC
Created July 9, 2010 (15 years, 11 months ago)
Expires July 9, 2026 (3 months)
Last Updated July 17, 2025
Name Servers ns41.domaincontrol.com, ns42.domaincontrol.com
DNSSEC Not enabled
Hosting
IP Address 23.227.38.32
ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)
Provider Cloudflare
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

A+
HTTP Probe Timing
Total 41 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
20 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
8 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
42 ms
Total Time Total request time from DNS lookup through full response.
42 ms

Connection waterfall

DNS Lookup 20 ms TCP Connect 1 ms TLS Handshake 8 ms Server Processing 13 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback