Skip to content
https://pnpm.io

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
6
INFO
1
Probed from New York, United Stated
200 OK
Checks
9
6 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
47 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

47
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, 10 ms lookup
PASS
2 A records, 10 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 76.76.21.241, 66.33.60.193
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: amir.ns.cloudflare.com, kate.ns.cloudflare.com
Info::
3 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: 10 ms
Got: 10 ms
A76.76.21.241, 66.33.60.193
AAAA—
CNAME—
NSamir.ns.cloudflare.com, kate.ns.cloudflare.com
MX
24 linda.mx.cloudflare.net
43 amir.mx.cloudflare.net
97 isaac.mx.cloudflare.net
TXT
brave-ledger-verification=39b6d13622f644b670f37187d3a58ea4b7a94b82dac2aa4793c697...
keybase-site-verification=dRYKp5DpU_VgraXbRT7dHJYm5gBKdQQUv4L912anldo
SPF v=spf1 include:_spf.mx.cloudflare.net ~all
t-verify=938b3051c50808d8fc93eb60327a1210
CAALookup not available with standard resolver
Resolved in 10 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://pnpm.io

https://pnpm.io

40 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://pnpm.io20040 msHTTP/1.1Vercel
A
Crawlability
no robots.txt, sitemap with 329 URLs
PASS
no robots.txt, sitemap with 329 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 329 entries

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 URL Set URLs 329 entries Valid XML Yes
Sample URLs:
A
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

308https://www.pnpm.io/
200https://pnpm.io/

HTTP → HTTPS

308http://pnpm.io/ → https://pnpm.io/

Use 301 (permanent) instead of 302 (temporary)

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

Connection waterfall

DNS Lookup 8 ms TCP Connect 1 ms TLS Handshake 18 ms Server Processing 16 ms Content Transfer 1 ms
A+
CDN & Delivery
Vercel (HIT)
PASS
Vercel (HIT)
Info::
Site is served via Vercel CDN
Got: x-vercel-id: iad1::xbpqn-1775328130736-b21b84e282ce
Info::
CDN cache status: HIT
CDN Detected: Vercel
Provider Vercel Cache Status HIT Evidence x-vercel-id: iad1::xbpqn-1775328130736-b21b84e282ce
Domain Intelligence
Domain intelligence data not available
INFO
Domain intelligence data not available

RDAP and WHOIS lookup both failed

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback