Skip to content
https://prettier.io

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
89
GRADE
B
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from New York, United Stated
200 OK
Checks
9
6 PASS 3 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
85 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

85
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
B
CDN & Delivery
Netlify
REVIEW
Netlify
Info::
Site is served via Netlify CDN
Got: x-nf-request-id: 01KNCW125N9P2YS51PYTS7F29Z
CDN Detected: Netlify
Provider Netlify Evidence x-nf-request-id: 01KNCW125N9P2YS51PYTS7F29Z
A+
DNS Records
1 A records, 28 ms lookup
PASS
1 A records, 28 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 104.198.14.52
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: edna.ns.cloudflare.com, norm.ns.cloudflare.com
Info::
No MX records — email not configured via DNS
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: 28 ms
Got: 28 ms
A104.198.14.52
AAAA
CNAME
NSedna.ns.cloudflare.com, norm.ns.cloudflare.com
MX
TXT
SPF v=spf1 a -all
CAALookup not available with standard resolver
Resolved in 28 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://prettier.io

https://prettier.io

197 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://prettier.io200197 msHTTP/1.1Netlify
A
Crawlability
no robots.txt, sitemap with 102 URLs
PASS
no robots.txt, sitemap with 102 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 102 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.

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.prettier.io/
200https://prettier.io/

Preferred variant: non-www

HTTP → HTTPS

301http://prettier.io/ https://prettier.io/

Consistent

A
Domain Intelligence
prettier.io — via RegistrarSEC LLC, 8 years, 11 months old, hosted on Google Cloud
PASS
prettier.io — via RegistrarSEC LLC, 8 years, 11 months old, hosted on Google Cloud
Warning::
Domain expires in 71 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jun 15, 2026
Info::
Registrar: RegistrarSEC LLC
Info::
Hosting: Google Cloud
Got: AS396982
Domain expiry

Expires today

June 15, 2026

SSL certificate

85 days

Issued by Let's Encrypt

Domain age

8 years, 11 months

Registered June 15, 2017

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Google Cloud

ASN AS396982

104.198.14.52

Registrar

RegistrarSEC LLC

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 RegistrarSEC LLC
Created June 15, 2017 (8 years, 11 months ago)
Expires June 15, 2026 (2 months)
Last Updated June 20, 2023
Name Servers norm.ns.cloudflare.com, edna.ns.cloudflare.com
Registrant Meta Platforms, Inc.
Hosting
IP Address 104.198.14.52
ASN AS396982 (GOOGLE-CLOUD-PLATFORM - Google LLC, US)
Provider Google Cloud
Data source: whois (0.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 208 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
9 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
64 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
67 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
208 ms
Total Time Total request time from DNS lookup through full response.
208 ms

Connection waterfall

DNS Lookup 9 ms TCP Connect 64 ms TLS Handshake 67 ms Server Processing 67 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