Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.CCrawlabilityActionrobots.txt present, sitemap with 0 URLsREVIEW
Search engines may not be able to parse the sitemap. Fix XML validation errors.
An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.
Learn more ▾ ▴
Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.
Source: sitemaps.org / Google Search Central
An empty sitemap provides no value. Add <url> entries for your pages.
An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.
Learn more ▾ ▴
Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.
Source: Google Search Central / sitemaps.org
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
<!doctype html><html lang="en"><head><script type="module" src="https://logseq.com/index.5cad6fbd.js"></script><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=5.0, minimum-scale=1.0"><meta http-equiv="X-UA-Compatible" content="ie=edge"><title>Logseq: A privacy-first, open-source knowledge base</title><link href="https://asset.logseq.com/static/img/logo.png" rel="icon shortcut" type="image/png"><link href="https://asset.logseq.com/static/img/logo.png" rel="icon shortcut" sizes="192x192"><link href="https://asset.logseq.com/static/img/logo.png" rel="apple-touch-icon"><meta content="Logseq" name="apple-mobile-web-app-title"><meta content="yes" name="apple-mobile-web-app-capable"><meta content="yes" name="apple-touch-fullscreen"><meta content="black-translucent" name="apple-mobile-web-app-status-bar-style"><meta content="yes" name="mobile-web-app-capable"><meta content="summary_large_image" name="twitter:card"><meta content="A privacy-first, open-source platform for knowledge management and collaboration." name="twitter:description"><meta content="@logseq" name="twitter:site"><meta content="A privacy-first, open-source knowledge base" name="twitter:title"><meta content="https://asset.logseq.com/static/img/social-banner-230118.png" name="twitter:image:src"><meta content="A privacy-first, open-source platform for knowledge management and collaboration." name="twitter:image:alt"><meta content="A privacy-first, open-source knowledge base" property="og:title"><meta content="site" property="og:type"><meta content="https://logseq.com" property="og:url"><meta content="https://asset.logseq.com/static/img/social-banner-230118.png" property="og:image"><meta content="A privacy-first, open-source platform for knowledge management and collaboration." property="og:description"><meta content="logseq" property="og:site_name"><meta description="A privacy-first, open-source platform for knowledge management and collaboration."><link rel="stylesheet" href="https://logseq.com/index.5f582d11.css"></head><body> <div id="root"></div> <script src="https://assets.lemonsqueezy.com/lemon.js" defer></script> <script src="https://logseq.com/index.4a951e2d.js" type="module" defer></script> </body></html>
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations278 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
- 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
BCDN & DeliveryAWS CloudFront (FunctionGeneratedResponse from cloudfront)REVIEW
ADNS Records4 A records, 48 ms lookupPASS
| A | 3.174.18.10, 3.174.18.8, 3.174.18.55, 3.174.18.88 |
| AAAA | 2600:9000:28e5:e600:7:4af5:2d40:93a1, 2600:9000:28e5:7200:7:4af5:2d40:93a1, 2600:9000:28e5:4e00:7:4af5:2d40:93a1, 2600:9000:28e5:5e00:7:4af5:2d40:93a1, 2600:9000:28e5:1800:7:4af5:2d40:93a1, 2600:9000:28e5:f800:7:4af5:2d40:93a1, 2600:9000:28e5:f600:7:4af5:2d40:93a1, 2600:9000:28e5:6a00:7:4af5:2d40:93a1 |
| CNAME | d4bsh8m6mdqd1.cloudfront.net |
| NS | ns-952.awsdns-55.net, ns-184.awsdns-23.com, ns-1562.awsdns-03.co.uk, ns-1489.awsdns-58.org |
| MX | — |
| TXT | — |
| CAA | Lookup not available with standard resolver |
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.
Learn more ▾ ▴
RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.
Source: RFC 1034
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
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'.
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)
ARedirect Chain1 redirect(s), 364 ms totalPASS
https://www.logseq.com
162 ms · HTTP/1.1
https://logseq.com/
203 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://www.logseq.com | 301 | 162 ms | HTTP/1.1 | CloudFront |
| 2 | https://logseq.com/ | 200 | 203 ms | HTTP/1.1 | AmazonS3 |
See the visual redirect chain in the HTTP Probe tab →
A+IPv6 ReadinessIPv6 reachable (57 ms)PASS
A+Domain Intelligencelogseq.com — via Amazon Registrar, Inc., 6 years old, hosted on AWSPASS
271 days
April 9, 2027
278 days
Issued by Amazon
6 years
Registered April 9, 2020
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
3.174.18.88
Amazon Registrar, Inc.
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
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