Skip to content
https://jestjs.io

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
92
GRADE
A
FIX
0
REVIEW
2
PASS
7
INFO
0
Probed from Singapore, Singapore
200 OK
Checks
9
7 PASS 2 REVIEW
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
58 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

58
days left
0d 30d 60d 90d+

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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
2 A records, 5114 ms lookup
PASS
2 A records, 5114 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.18.20.144, 104.18.21.144
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700::6812:1590, 2606:4700::6812:1490
Info::
2 nameserver(s) configured
Got: tate.ns.cloudflare.com, stevie.ns.cloudflare.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
Warning::
DNS resolution is slow (5114 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 5114 ms
A104.18.20.144, 104.18.21.144
AAAA2606:4700::6812:1590, 2606:4700::6812:1490
CNAME
NState.ns.cloudflare.com, stevie.ns.cloudflare.com
MX
10 eforward2.registrar-servers.com
10 eforward3.registrar-servers.com
10 eforward1.registrar-servers.com
15 eforward4.registrar-servers.com
20 eforward5.registrar-servers.com
TXT
ALIAS for jestjs.netlify.app
SPF v=spf1 include:spf.efwd.registrar-servers.com ~all
CAALookup not available with standard resolver
Resolved in 5114 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.

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://jestjs.io

https://jestjs.io

75 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://jestjs.io20075 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2606:4700::6812:1590, 2606:4700::6812:1490
Got: 1 ms connect
IPv6 Ready
AAAA Records 2606:4700::6812:1590, 2606:4700::6812:1490 Connection Reachable (1 ms)
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.jestjs.io/
200https://jestjs.io/

Preferred variant: non-www

HTTP → HTTPS

301http://jestjs.io/ https://jestjs.io/

Consistent

A
Domain Intelligence
jestjs.io — via 1API GmbH, 7 years, 10 months old
PASS
jestjs.io — via 1API GmbH, 7 years, 10 months old
Warning::
Domain expires in 82 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jun 25, 2026
Info::
Registrar: 1API GmbH
Domain expiry

10 days

June 25, 2026

SSL certificate

58 days

Issued by Google Trust Services

Domain age

7 years, 10 months

Registered June 25, 2018

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

2606:4700::6812:1590

Registrar

1API GmbH

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
Registrar 1API GmbH
Created June 25, 2018 (7 years, 10 months ago)
Expires June 25, 2026 (2 months)
Last Updated November 26, 2025
Name Servers stevie.ns.cloudflare.com, tate.ns.cloudflare.com
Registrant Jest
Hosting
IP Address 2606:4700::6812:1590
Data source: whois (2.8s)

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

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

Connection waterfall

DNS Lookup 242 ms TCP Connect 1 ms TLS Handshake 10 ms Server Processing 20 ms Content Transfer 0 ms
A
CDN & Delivery
Cloudflare (DYNAMIC)
PASS
Cloudflare (DYNAMIC)
Info::
Site is served via Cloudflare CDN (edge: SIN)
Got: cf-ray: 9e72737e9aa06004-SIN
Info::
CDN cache status: DYNAMIC
CDN Detected: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: 9e72737e9aa06004-SIN
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback