Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BTLS Certificate Expiry & Recommendations225 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
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
ADNS Records4 A records, 27 ms lookupPASS
| A | 18.161.111.56, 18.161.111.47, 18.161.111.119, 18.161.111.44 |
| AAAA | 2600:9000:23d1:c00:e:8499:1080:93a1, 2600:9000:23d1:7e00:e:8499:1080:93a1, 2600:9000:23d1:1200:e:8499:1080:93a1, 2600:9000:23d1:6e00:e:8499:1080:93a1, 2600:9000:23d1:8200:e:8499:1080:93a1, 2600:9000:23d1:9800:e:8499:1080:93a1, 2600:9000:23d1:4800:e:8499:1080:93a1, 2600:9000:23d1:3000:e:8499:1080:93a1 |
| CNAME | — |
| NS | — |
| MX | — |
| TXT | — |
| CAA | Lookup not available with standard resolver |
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)
A+Redirect ChainNo redirects — direct accessPASS
https://www.todoist.com
153 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://www.todoist.com | 200 | 153 ms | HTTP/1.1 |
A+IPv6 ReadinessIPv6 reachable (20 ms)PASS
ACrawlabilityno robots.txt, sitemap with 19 URLsPASS
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
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
No robots.txt found
This is fine for most sites — a missing robots.txt allows all crawling by default.
- https://www.todoist.com/sitemap-0.xml
- https://www.todoist.com/sitemap-1.xml
- https://www.todoist.com/sitemap-2.xml
- https://www.todoist.com/sitemap-3.xml
- https://www.todoist.com/sitemap-4.xml
- https://www.todoist.com/sitemap-5.xml
- https://www.todoist.com/sitemap-6.xml
- https://www.todoist.com/sitemap-7.xml
- https://www.todoist.com/sitemap-8.xml
- https://www.todoist.com/sitemap-9.xml
- https://www.todoist.com/sitemap-10.xml
- https://www.todoist.com/sitemap-11.xml
- https://www.todoist.com/sitemap-12.xml
- https://www.todoist.com/sitemap-13.xml
- https://www.todoist.com/sitemap-14.xml
- https://www.todoist.com/sitemap-15.xml
- https://www.todoist.com/sitemap-16.xml
- https://www.todoist.com/sitemap-17.xml
- https://www.todoist.com/sitemap-18.xml
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: www
HTTP → HTTPS
Consistent
A+Domain Intelligencetodoist.com — via Amazon Registrar, Inc., 19 years, 6 months oldPASS
177 days
January 5, 2027
225 days
Issued by Amazon
19 years, 6 months
Registered January 5, 2007
Not enabled
Protects against DNS spoofing
Unknown
2600:9000:2921:600:1f:9a86:8040:93a1
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