Skip to content
https://nutrimuscle.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 Madrid, Spain
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
80 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

80
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: CDG)
Got: cf-ray: 9e8fd4140fcc7029-CDG
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9e8fd4140fcc7029-CDG
A+
DNS Records
1 A records, 41 ms lookup
PASS
1 A records, 41 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 23.227.38.65
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
3 nameserver(s) configured
Got: ns-93-b.gandi.net, ns-13-a.gandi.net, ns-103-c.gandi.net
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: 41 ms
Got: 41 ms
A23.227.38.65
AAAA
CNAME
NSns-93-b.gandi.net, ns-13-a.gandi.net, ns-103-c.gandi.net
MX
0 nutrimuscle-com.mail.protection.outlook.com
TXT
_globalsign-domain-verification=zbPaGfe-SKmJSTBrg5lYiyi99HD39Pmvymte3H-sPx
google-site-verification=60nx4JoQSgJTstPIycsWS-d-IVb0sr9c7NYZ4sfVxg8
MS=ms23232581
klaviyo-site-verification=T9argN
klaviyo-site-verification=WFksXh
klaviyo-site-verification=UQNz9B
apple-domain-verification=2JjhdxU1uQmNvaAb
SPF v=spf1 include:spf.protection.outlook.com include:amazonses.com include:mailgun....
klaviyo-site-verification=TdYQd9
klaviyo-site-verification=TKZTj9
google-site-verification=cETSUEf5skOoY9h6ZlDFi6FJEmr9tg5VQNMllOOSuzs
klaviyo-site-verification=XE3MyX
tpx9yvshrdvcqw0tc297y49vbq42kptb
google-site-verification=9GFWlOb1Mdu8ToK_wZkVbT-sLK7R7BAF5RpNcO1pUR4
Sendinblue-code:b85c9644df119db44a6c83afed0990cf
CAALookup not available with standard resolver
Resolved in 41 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), 65 ms total
PASS
0 redirect(s), 65 ms total

https://nutrimuscle.com

65 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://nutrimuscle.com42965 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.nutrimuscle.com/
200https://nutrimuscle.com/

HTTP → HTTPS

301http://nutrimuscle.com/ https://nutrimuscle.com/

Consistent

A+
Domain Intelligence
nutrimuscle.com — via Gandi SAS, 22 years, 5 months old, hosted on Cloudflare
PASS
nutrimuscle.com — via Gandi SAS, 22 years, 5 months old, hosted on Cloudflare
Info::
Domain registered until Feb 3, 2027 (10 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: Gandi SAS
Info::
Hosting: Cloudflare
Got: AS13335
Domain expiry

233 days

February 3, 2027

SSL certificate

80 days

Issued by Let's Encrypt

Domain age

22 years, 5 months

Registered February 3, 2004

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

23.227.38.65

Registrar

Gandi SAS

Lock status unknown 3 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
Registrar Gandi SAS
Created February 3, 2004 (22 years, 5 months ago)
Expires February 3, 2027 (10 months)
Last Updated January 3, 2026
Name Servers ns-103-c.gandi.net, ns-13-a.gandi.net, ns-93-b.gandi.net
DNSSEC Not enabled
Hosting
IP Address 23.227.38.65
ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)
Provider Cloudflare
Data source: rdap (0.1s)

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 104 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.
16 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
22 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
105 ms
Total Time Total request time from DNS lookup through full response.
105 ms

Connection waterfall

DNS Lookup 40 ms TCP Connect 16 ms TLS Handshake 22 ms Server Processing 26 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