Skip to content
https://a16z.com

Infrastructure

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

Certificate validity

75
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
B
CDN & Delivery
Netlify
REVIEW
Netlify
Info::
Site is served via Netlify CDN
Got: x-nf-request-id: 01KPVH9HNHT70B2297C0E6PN1B
CDN Detected: Netlify
Provider Netlify Evidence x-nf-request-id: 01KPVH9HNHT70B2297C0E6PN1B
A+
DNS Records
1 A records, 20 ms lookup
PASS
1 A records, 20 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 75.2.60.5
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ha1.markmonitor.zone, ha2.markmonitor.zone, ha3.markmonitor.zone, ha4.markmonitor.zone
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: 20 ms
Got: 20 ms
A75.2.60.5
AAAA
CNAME
NSha1.markmonitor.zone, ha2.markmonitor.zone, ha3.markmonitor.zone, ha4.markmonitor.zone
MX
10 aspmx.l.google.com
20 alt1.aspmx.l.google.com
30 alt2.aspmx.l.google.com
40 aspmx2.googlemail.com
50 aspmx3.googlemail.com
TXT
MS=ms78121488
a5ml0q2qredqkscjd0cnd3rs5o
TAILSCALE-hgqvPubwp5HFczvxm0V3
ZOOM_verify_CZpP8WiXT3CuvCsqJO99fQ
MS=297F6982EA6FC1794C4BC3FB5FF63A8E4CD4FAC4
ccisso=ccd758c0-2760-47f8-a10d-e5fc116fddae
affinity-allowed-subdomains=a16z,a16z-crypto
jamf-site-verification=r5S6YMFCZk83AroC1PcG8w
1password-site-verification=YNM3U5T3JZG5PEII74IIUKCOLQ
elevenlabs=27i8sF6BnzYwPsZ5yq5TdjVJ000nf-OvqH4jBvfEnAQ
openai-domain-verification=dv-CeeBac0VpbCCPpKaEHijwN7V
gamma-domain-verification-gp4vsa=J4Meie8RekYZa4fxKQ5kuayqy
cursor-domain-verification-7pnt8f=k0kHfixkiuNQWkL4COkqeKER8
anthropic-domain-verification-afe4hb=TrYvFm4pI5i7OwaiQnLdjFmZi
perplexity-ai-domain-verification-66m0r7=3MZMPYJPZOdMXMDKTQAozQpXs
google-site-verification=Cda284zEu8xh5veDdCm00SdfO_tJF-ebT809nkgB1zA
censys-domain-verification=J1TG-Io7I9BckAxCWrurh86BYAQZGVEmTynNV9awatzH
h1-domain-verification=vkosaeLv5aMSu6gt7GRxtajukLQ3hKGixbfbe9ZWR8VwKYf9
mgverify=0fe09ec683f6868bb8547d3edcd914093dd94e3957094a60fe4f5e496b2b9745
zapier-domain-verification-challenge=f9cf9944-aaa7-4e2b-aabf-d2a392c18e0c
neat-pulse-domain-verification-4wMj96X=d2d2ebff-e37e-4bac-9efc-a5b0e583a0d4
hubspot-domain-verification=MWVlYzc1MzAtMzY4MC00MzNkLTk0NGQtOWU2Y2I3MTJiZDI2
SPF v=spf1 include:_spf.google.com include:_spf.salesforce.com include:spf.happyfox....
notion_verify_FvVFn84Y5fBnAntNFUjAg1p8Mox5n8sVJtGGVpmMeKV3PNqhbTdF1MsP5gWvM08GZq...
stripe-verification=FC0027ACED84DA245559E90AA0BE435C9D507EE24C5CF17AFD11316B9808...
wiz-domain-verification=5dc014a9a7637634bf88686260016ef95998390f9f1703e28716979f...
atlassian-domain-verification=afgyuWvgwYP6dShfPqgKfpNFXkbap4546WDp6lt8DCGR1IykT5...
CAALookup not available with standard resolver
Resolved in 20 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://a16z.com

https://a16z.com

138 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://a16z.com200138 msHTTP/1.1Netlify
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.a16z.com/
200https://a16z.com/

Preferred variant: non-www

HTTP → HTTPS

301http://a16z.com/ https://a16z.com/

Consistent

A+
Domain Intelligence
a16z.com — via MarkMonitor Inc., 17 years, 5 months old, hosted on AWS
PASS
a16z.com — via MarkMonitor Inc., 17 years, 5 months old, hosted on AWS
Info::
Domain registered until Jan 13, 2028 (1 years, 9 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: MarkMonitor Inc.
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Info::
Hosting: AWS
Got: AS16509
Domain expiry

579 days

January 13, 2028

SSL certificate

75 days

Issued by Let's Encrypt

Domain age

17 years, 5 months

Registered January 26, 2009

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

75.2.60.5

Registrar

MarkMonitor Inc.

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar MarkMonitor Inc.
Created January 26, 2009 (17 years, 5 months ago)
Expires January 13, 2028 (1 years, 9 months)
Last Updated December 12, 2025
Name Servers ha1.markmonitor.zone, ha2.markmonitor.zone, ha3.markmonitor.zone, ha4.markmonitor.zone
DNSSEC Not enabled
Hosting
IP Address 75.2.60.5
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.1s)

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

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A+
HTTP Probe Timing
Total 193 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
6 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
4 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
7 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
142 ms
Total Time Total request time from DNS lookup through full response.
193 ms

Connection waterfall

DNS Lookup 6 ms TCP Connect 4 ms TLS Handshake 7 ms Server Processing 124 ms Content Transfer 52 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback