Skip to content
https://supabase.com

Infrastructure

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

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • 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, 5 ms lookup
PASS
1 A records, 5 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 216.150.1.193
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: christina.ns.cloudflare.com, neil.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
Info::
DNS resolution time: 5 ms
Got: 5 ms
A216.150.1.193
AAAA
CNAME
NSchristina.ns.cloudflare.com, neil.ns.cloudflare.com
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 alt3.aspmx.l.google.com
10 alt4.aspmx.l.google.com
TXT
google-site-verification=LvTSpLp-EquMSIYv-4caP8Rln0kqiVgXMfZT5jOA_Ro
ZOOM_verify_LkQKLCEOSZMkt2ZfWZsQoF
google-site-verification=iZqSVmPnujGxdyqGRFI5cKMrdHUL8zIR_GcLd8D2XiA
SPF v=spf1 include:_spf.google.com include:19953346.spf06.hubspotemail.net ~all
google-site-verification=ouqZams1dXBRlKsMoYhfaKk02ciAP_LnSrDLXznbasc
CAALookup not available with standard resolver
Resolved in 5 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://supabase.com

https://supabase.com

56 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://supabase.com20056 msHTTP/1.1Vercel
A+
Crawlability
robots.txt present, sitemap with 2 URLs
PASS
robots.txt present, sitemap with 2 URLs
Info::
robots.txt is present
Got: 55 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 2 entries
Info::
Sitemap index with 2 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 55 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Sitemap: https://supabase.com/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 2 entries Valid XML Yes
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)
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

301https://www.supabase.com/
200https://supabase.com/

Preferred variant: non-www

HTTP → HTTPS

308http://supabase.com/ https://supabase.com/

Use 301 (permanent) instead of 302 (temporary)

A+
Domain Intelligence
supabase.com — via Amazon Registrar, Inc., 8 years, 7 months old, hosted on AWS
PASS
supabase.com — via Amazon Registrar, Inc., 8 years, 7 months old, hosted on AWS
Info::
Domain registered until Sep 24, 2026 (5 months remaining)
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: Amazon Registrar, Inc.
Info::
Hosting: AWS
Got: AS16509
Domain expiry

74 days

September 24, 2026

SSL certificate

64 days

Issued by Let's Encrypt

Domain age

8 years, 7 months

Registered September 24, 2017

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

216.150.1.193

Registrar

Amazon Registrar, Inc.

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
  • Enable DNSSEC to protect visitors from DNS spoofing
Registrar Amazon Registrar, Inc.
Created September 24, 2017 (8 years, 7 months ago)
Expires September 24, 2026 (5 months)
Last Updated August 20, 2025
Name Servers christina.ns.cloudflare.com, neil.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 216.150.1.193
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.7s)

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

A+
HTTP Probe Timing
Total 74 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
3 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.
71 ms
Total Time Total request time from DNS lookup through full response.
75 ms

Connection waterfall

DNS Lookup 3 ms TCP Connect 1 ms TLS Handshake 18 ms Server Processing 48 ms Content Transfer 4 ms
A+
CDN & Delivery
Vercel (HIT)
PASS
Vercel (HIT)
Info::
Site is served via Vercel CDN
Got: x-vercel-id: fra1::kkxr7-1775321391707-4bfe53ea0f0e
Info::
CDN cache status: HIT
CDN Detected: Vercel
Provider Vercel Cache Status HIT Evidence x-vercel-id: fra1::kkxr7-1775321391707-4bfe53ea0f0e
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback