Skip to content
https://www.obsidian.md

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
89
GRADE
B
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 4 REVIEW
B
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 23 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 23 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *

Allow: /
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.obsidian.md/
200https://obsidian.md/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://www.obsidian.md/ https://obsidian.md/

Consistent

B
TLS Certificate Expiry & Recommendations
83 days until leaf cert expires — 5 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • 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
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: 9e8bd36bdddf9ec2-CDG
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9e8bd36bdddf9ec2-CDG
A
DNS Records
3 A records, 78 ms lookup
PASS
3 A records, 78 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 104.26.1.147, 104.26.0.147, 172.67.74.64
Info::
Has 3 IPv6 (AAAA) record(s)
Got: 2606:4700:20::ac43:4a40, 2606:4700:20::681a:93, 2606:4700:20::681a:193
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: 78 ms
Got: 78 ms
A104.26.1.147, 104.26.0.147, 172.67.74.64
AAAA2606:4700:20::ac43:4a40, 2606:4700:20::681a:93, 2606:4700:20::681a:193
CNAME
NS
MX
TXT
CAALookup not available with standard resolver
Resolved in 78 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
1 redirect(s), 175 ms total
PASS
1 redirect(s), 175 ms total
Info::
Single redirect
Got: https://www.obsidian.md → https://obsidian.md/ (301)
Info::
WWW normalization redirect

https://www.obsidian.md

65 ms · HTTP/1.1

301

https://obsidian.md/

110 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.obsidian.md30165 msHTTP/1.1cloudflare
2https://obsidian.md/200110 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700:20::ac43:4a40, 2606:4700:20::681a:93, 2606:4700:20::681a:193
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700:20::ac43:4a40, 2606:4700:20::681a:93, 2606:4700:20::681a:193 Connection Reachable (17 ms)
A+
Domain Intelligence
obsidian.md — 6 years, 1 months old
PASS
obsidian.md — 6 years, 1 months old
Info::
Domain registered until Mar 13, 2028 (1 years, 11 months remaining)
Domain expiry

610 days

March 13, 2028

SSL certificate

83 days

Issued by Google Trust Services

Domain age

6 years, 1 months

Registered March 13, 2020

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

2606:4700:20::ac43:4a40

Registrar

Registrar unknown

Lock status unknown 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar
Created March 13, 2020 (6 years, 1 months ago)
Expires March 13, 2028 (1 years, 11 months)
Name Servers lloyd.ns.cloudflare.com, olga.ns.cloudflare.com
Hosting
IP Address 2606:4700:20::ac43:4a40
Data source: whois (0.7s)
A+
HTTP Probe Timing
Total 138 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
80 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
16 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
22 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
138 ms
Total Time Total request time from DNS lookup through full response.
138 ms

Connection waterfall

DNS Lookup 80 ms TCP Connect 16 ms TLS Handshake 22 ms Server Processing 20 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