Skip to content
https://bio.site

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
0
REVIEW
2
PASS
7
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
7 PASS 2 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
TLS Certificate Expiry & Recommendations
46 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

46
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
4 A records, 37 ms lookup
PASS
4 A records, 37 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 151.101.66.132, 151.101.2.132, 151.101.130.132, 151.101.194.132
Info::
No IPv6 (AAAA) records
Info::
8 nameserver(s) configured
Got: ns03.squarespacedns.com, ns02.squarespacedns.com, dns2.p02.nsone.net, dns1.p02.nsone.net, dns4.p02.nsone.net, dns3.p02.nsone.net, ns01.squarespacedns.com, ns04.squarespacedns.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: 37 ms
Got: 37 ms
A151.101.66.132, 151.101.2.132, 151.101.130.132, 151.101.194.132
AAAA—
CNAME—
NSns03.squarespacedns.com, ns02.squarespacedns.com, dns2.p02.nsone.net, dns1.p02.nsone.net, dns4.p02.nsone.net, dns3.p02.nsone.net, ns01.squarespacedns.com, ns04.squarespacedns.com
MX
10 eforward3.registrar-servers.com
10 eforward1.registrar-servers.com
10 eforward2.registrar-servers.com
15 eforward4.registrar-servers.com
20 eforward5.registrar-servers.com
TXT
google-site-verification=y-fN-brSF4T5hh4x600-U0BMABQy1Ad5iKY8t2Qg-84
SPF v=spf1 include:spf.efwd.registrar-servers.com ~all
CAALookup not available with standard resolver
Resolved in 37 ms

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), 46 ms total
PASS
1 redirect(s), 46 ms total
Info::
Single redirect
Got: https://bio.site → https://biosites.com/ (301)
Info::
Cross-domain redirect detected

https://bio.site

3 ms · HTTP/1.1

301

https://biosites.com/

43 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://bio.site3013 msHTTP/1.1
2https://biosites.com/20043 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A
Crawlability
no robots.txt, sitemap with 55 URLs
PASS
no robots.txt, sitemap with 55 URLs
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 55 entries
Info::
Sitemap index with 55 child sitemaps

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

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 200 OK
Type Sitemap Index URLs 55 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.bio.site/
200https://bio.site/

Preferred variant: non-www

HTTP → HTTPS

301http://bio.site/ → https://biosites.com/

Consistent

A
Domain Intelligence
bio.site — via MarkMonitor Inc., 5 years, 10 months old, hosted on Fastly
PASS
bio.site — via MarkMonitor Inc., 5 years, 10 months old, hosted on Fastly
Warning::
Domain expires in 89 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jul 20, 2026
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: MarkMonitor Inc.
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Info::
Hosting: Fastly
Got: AS54113
Domain expiry

3 days

July 20, 2026

SSL certificate

46 days

Issued by Let's Encrypt

Domain age

5 years, 10 months

Registered July 20, 2020

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Fastly

ASN AS54113

151.101.130.132

Registrar

MarkMonitor Inc.

Unlocked 8 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
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar MarkMonitor Inc.
Created July 20, 2020 (5 years, 10 months ago)
Expires July 20, 2026 (2 months)
Last Updated July 12, 2024
Name Servers dns1.p03.nsone.net, dns2.p03.nsone.net, dns3.p03.nsone.net, dns4.p03.nsone.net, ns01.squarespacedns.com, ns02.squarespacedns.com, ns03.squarespacedns.com, ns04.squarespacedns.com
DNSSEC Not enabled
Hosting
IP Address 151.101.130.132
ASN AS54113 (FASTLY - Fastly, Inc., US)
Provider Fastly
Data source: rdap (0.7s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more ▾

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

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

Connection waterfall

DNS Lookup 17 ms TCP Connect 0 ms TLS Handshake 2 ms Server Processing 1 ms Content Transfer 0 ms
A+
CDN & Delivery
Fastly (HIT)
PASS
Fastly (HIT)
Info::
Site is served via Fastly CDN
Got: x-served-by: cache-toj-leto2350026-TOJ
Info::
CDN cache status: HIT
CDN Detected: Fastly
Provider Fastly Cache Status HIT Evidence x-served-by: cache-toj-leto2350026-TOJ
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback