tailscale.com

Readiness by lane

Green: tailscale.com. Thin bar: Security & Monitoring peer median.

Priority fixes for tailscale.com

Ordered by impact and by how common each practice is among peers.

1. Priority 1 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 1 external script without async or defer.

   Why it matters: A plain <script src> in the head stops the browser from showing anything until that file has downloaded and run.

   What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.

   On Next.js: Use the next/script component with an appropriate loading strategy.

   47% of Security & Monitoring peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.

   Guide: Control Third-Party Scripts Before They Control Your Page

2. Priority 2 · Accelerate

   HTTP/3 advertised

   Observed: The homepage did not advertise HTTP/3 through an Alt-Svc header.

   What to do: Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.

   40% of Security & Monitoring peers do this.

   Guide: CDN Guide for Website Owners

3. Priority 3 · Enable

   Structured data present

   Observed: The homepage had no JSON-LD structured data.

   What to do: Add JSON-LD for your organization and main content types, then test it with Google's Rich Results Test.

   51% of Security & Monitoring peers do this.

   Guide: Structured Data Basics for Website Owners

4. Priority 4 · Harden

   DNSSEC signed

   Observed: No DS record was found for tailscale.com at its parent zone, so its DNS answers are not DNSSEC-signed.

   What to do: Enable DNSSEC at your DNS provider, then add the DS record at your registrar. Plan provider moves carefully: a stale DS record can make the domain fail to resolve.

   On Amazon Route 53: Enable DNSSEC signing for the hosted zone and establish the chain of trust at the registrar.

   2.2% of Security & Monitoring peers do this.

   Guide: Website Uptime Readiness: Prepare Before Traffic Arrives

What tailscale.com already does well

Practices fewer than half of Security & Monitoring peers use.

• security.txt publishedsecurity.txt with a contact found.12% of peers
• CAA records limit who can issue certificatesCAA limits issuance to amazon.com, amazonaws.com, amazontrust.com and others.18% of peers
• Content Security Policy presentContent-Security-Policy present.33% of peers

What we saw

Homepage checked

https://tailscale.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2026-12-13

CDN or edge

Vercel

Platform or framework

Next.js

DNS operators

Amazon Route 53

HSTS

max-age 730 days

DMARC policy

p=reject

Homepage HTML

283 KB, br

Images on homepage

54 (svg 54)

Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.

Stack and providers

Seen in the homepage response, certificate and DNS. Provider pages compare how their customers configure the same checks.

All 31 checks

Select a gap for the method and fix. How each check works

Compare with other Security & Monitoring sites

• feedly.com86
• guard.io71
• osirisai.live77
• spappmonitoring.com65
• truecaller.com79

Security & Monitoring readiness benchmark