Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations37 days until leaf cert expires — 5 issues to addressREVIEW
Certificate validity
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
BCDN & DeliveryCloudflareREVIEW
ADNS Records2 A records, 32 ms lookupPASS
| A | 104.18.2.84, 104.18.3.84 |
| AAAA | 2606:4700::6812:254, 2606:4700::6812:354 |
| 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)
ARedirect Chain1 redirect(s), 336 ms totalPASS
https://www.superhuman.com
65 ms · HTTP/1.1
https://superhuman.com/
271 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://www.superhuman.com | 301 | 65 ms | HTTP/1.1 | cloudflare |
| 2 | https://superhuman.com/ | 200 | 271 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
A+IPv6 ReadinessIPv6 reachable (17 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 6 URLsPASS
User-agent: *
Allow: /
Allow: /api/initLoad?*
Disallow: /*?
Disallow: /*@
Disallow: /tag/
Disallow: /admin
Disallow: /refer
Disallow: /refer/
Disallow: /invite/
Disallow: /tagged/
Disallow: /signup
Disallow: /welcome
Disallow: /profile
Disallow: /onboarding
Disallow: /mail/settings
User-agent: Twitterbot
Allow: /refer/
Allow: /invite/
User-agent: facebookexternalhit
Allow: /refer/
Allow: /invite/
User-agent: LinkedInBot
Allow: /refer/
Allow: /invite/
User-agent: Telegrambot
Allow: /refer/
Allow: /invite/
Sitemap: https://superhuman.com/sitemap_index.xml
Sitemap: https://help.superhuman.com/hc/sitemap.xml
Sitemap: https://blog.superhuman.com/sitemap.xml
A+Domain Intelligencesuperhuman.com — via Cloudflare, Inc., 26 years, 9 months oldPASS
3057 days
November 24, 2034
37 days
Issued by Google Trust Services
26 years, 9 months
Registered November 24, 1999
Not enabled
Protects against DNS spoofing
Unknown
2606:4700::6812:354
Cloudflare, 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