Skip to content
https://fruits.co

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Madrid, Spain
308 Permanent Redirect
Checks
9
4 PASS 4 REVIEW 1 FIX
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
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
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 142 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 142 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow:
Disallow: /api/
Disallow: /rss/
Disallow: /id/
Disallow: /c/
Disallow: /domain/
Disallow: /dashboard/
Disallow: /auth/
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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 301-redirects to HTTPS

www / non-www

200https://www.fruits.co/
200https://fruits.co/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://fruits.co/ https://fruits.co:443/

Consistent

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

Certificate validity

63
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
A+
DNS Records
1 A records, 42 ms lookup
PASS
1 A records, 42 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 34.107.155.91
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: ns-cloud-a3.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a1.googledomains.com, ns-cloud-a4.googledomains.com
Info::
5 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: 42 ms
Got: 42 ms
A34.107.155.91
AAAA
CNAME
NSns-cloud-a3.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a1.googledomains.com, ns-cloud-a4.googledomains.com
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 alt4.aspmx.l.google.com
10 alt3.aspmx.l.google.com
TXT
google-site-verification=gxeUj35QcmisV5wFGh2qvjmFaCINmCB8_hTSFhR1oN8
facebook-domain-verification=47ue750m5he7c0ch0oinvn2mj7hcj5
google-site-verification=AsZLYlSeDHESjZTsN_sOHudvXxQ71PJJyVkTPe51I2g
brevo-code:1b063e667e68ba0efe7361b8ed723738
SPF v=spf1 include:_spf.google.com include:sendgrid.net ~all
proxy-ssl.webflow.com
CAALookup not available with standard resolver
Resolved in 42 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
1 redirect(s), 212 ms total
PASS
1 redirect(s), 212 ms total
Info::
Single redirect
Got: https://fruits.co → https://www.fruits.co/ (308)
Info::
WWW normalization redirect

https://fruits.co

71 ms · HTTP/1.1

308

https://www.fruits.co/

142 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://fruits.co30871 msHTTP/1.1
2https://www.fruits.co/200142 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
Domain Intelligence
fruits.co — via united-domains GmbH, 16 years, 4 months old, hosted on Google Cloud
PASS
fruits.co — via united-domains GmbH, 16 years, 4 months old, hosted on Google Cloud
Info::
Domain registered until Feb 24, 2027 (10 months remaining)
Info::
Registrar: united-domains GmbH
Info::
Registrar lock is enabled
Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.
Info::
Hosting: Google Cloud
Got: AS396982
Domain expiry

256 days

February 24, 2027

SSL certificate

63 days

Issued by Google Trust Services

Domain age

16 years, 4 months

Registered February 25, 2010

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Google Cloud

ASN AS396982

34.107.155.91

Registrar

united-domains GmbH

Locked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar united-domains GmbH
Created February 25, 2010 (16 years, 4 months ago)
Expires February 24, 2027 (10 months)
Last Updated April 11, 2026
Name Servers ns-cloud-a3.googledomains.com, ns-cloud-a1.googledomains.com, ns-cloud-a4.googledomains.com, ns-cloud-a2.googledomains.com
Hosting
IP Address 34.107.155.91
ASN AS396982 (GOOGLE-CLOUD-PLATFORM - Google LLC, US)
Provider Google Cloud
Data source: whois (1.1s)

Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.

Why this matters

Registrar lock (clientTransferProhibited et al.) prevents unauthorized domain transfers — strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A+
HTTP Probe Timing
Total 114 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
47 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.
32 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
114 ms
Total Time Total request time from DNS lookup through full response.
115 ms

Connection waterfall

DNS Lookup 47 ms TCP Connect 17 ms TLS Handshake 32 ms Server Processing 18 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