Skip to content
https://www.notion.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
98
GRADE
A+
FIX
0
REVIEW
1
PASS
8
INFO
0
Probed from Amsterdam, Netherlands
200 OK
Checks
9
8 PASS 1 REVIEW
B
TLS Certificate Expiry & Recommendations
69 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

69
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
2 A records, 16 ms lookup
PASS
2 A records, 16 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 208.103.161.2, 208.103.161.1
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2602:f79a::1, 2602:f79a::2
Info::
No NS records found
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::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 16 ms
Got: 16 ms
A208.103.161.2, 208.103.161.1
AAAA2602:f79a::1, 2602:f79a::2
CNAME—
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 16 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.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.notion.com

https://www.notion.com

615 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.notion.com200615 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (2 ms)
PASS
IPv6 reachable (2 ms)
Info::
IPv6 is configured and reachable at 2602:f79a::1, 2602:f79a::2
Got: 2 ms connect
IPv6 Ready
AAAA Records 2602:f79a::1, 2602:f79a::2 Connection Reachable (2 ms)
A+
Crawlability
robots.txt present, sitemap with 201 URLs
PASS
robots.txt present, sitemap with 201 URLs
Info::
robots.txt is present
Got: 1246 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 201 entries
Info::
Sitemap index with 201 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1246 B Sitemaps referenced 14 User-agents *, BLEXBot, AhrefsBot, Amazonbot, SemrushBot, dotbot Blocking No — crawling allowed
User-Agent: *
Allow: /
Disallow: /invite/
Disallow: /*/invite/
Disallow: /templates/search?query=*
Disallow: /*/templates/search?query=*
Disallow: /experiment/*
Disallow: /*/experiment/*
Disallow: /lp/webinars/
Disallow: /lp/webinars/*
Disallow: /_vercel/insights/view
Disallow: /embed/*
Disallow: /*/embed/*
Disallow: /product/agents-homepage

User-Agent: BLEXBot
Disallow: /

User-Agent: AhrefsBot
Disallow: /

User-Agent: Amazonbot
Disallow: /

User-Agent: SemrushBot
Disallow: /

User-Agent: dotbot
Disallow: /

Sitemap: https://www.notion.com/sitemap.xml
Sitemap: https://sitemaps.notion.com/sitemap-categories.xml
Sitemap: https://sitemaps.notion.com/sitemap-collections.xml
Sitemap: https://www.notion.com/sitemap-root.xml
Sitemap: https://www.notion.com/blog/sitemap.xml
Sitemap: https://www.notion.com/customers/sitemap.xml
Sitemap: https://www.notion.com/help/sitemap.xml
Sitemap: https://www.notion.com/md/sitemap.xml
Sitemap: https://www.notion.com/pages/sitemap.xml
Sitemap: https://www.notion.com/product/sitemap.xml
Sitemap: https://www.notion.com/releases/sitemap.xml
Sitemap: https://www.notion.com/use-case/sitemap.xml
Sitemap: https://www.notion.com/feature/sitemap.xml
Sitemap: https://www.notion.com/front-static/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 201 entries Valid XML Yes
Child Sitemaps:
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: www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.notion.com/
302https://notion.com/

Preferred variant: www

HTTP → HTTPS

301http://www.notion.com/ → https://www.notion.com/

Consistent

A+
Domain Intelligence
notion.com — via Amazon Registrar, Inc., 28 years, 11 months old
PASS
notion.com — via Amazon Registrar, Inc., 28 years, 11 months old
Info::
Domain registered until Oct 5, 2033 (7 years, 7 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.
Domain expiry

2642 days

October 5, 2033

SSL certificate

69 days

Issued by Google Trust Services

Domain age

28 years, 11 months

Registered October 6, 1997

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2602:f79a::1

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
  • Enable DNSSEC to protect visitors from DNS spoofing
Registrar Amazon Registrar, Inc.
Created October 6, 1997 (28 years, 11 months ago)
Expires October 5, 2033 (7 years, 7 months)
Last Updated June 16, 2025
Name Servers dana.ns.cloudflare.com, woz.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2602:f79a::1
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

A
HTTP Probe Timing
Total 678 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.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
10 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
527 ms
Total Time Total request time from DNS lookup through full response.
679 ms

Connection waterfall

DNS Lookup 6 ms TCP Connect 1 ms TLS Handshake 10 ms Server Processing 510 ms Content Transfer 152 ms
A
CDN & Delivery
Cloudflare (DYNAMIC)
PASS
Cloudflare (DYNAMIC)
Info::
Site is served via Cloudflare CDN (edge: AMS)
Got: cf-ray: 9e8bae8d7d1b665b-AMS
Info::
CDN cache status: DYNAMIC
CDN Detected: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: 9e8bae8d7d1b665b-AMS
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback