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 & Recommendations214 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
A+DNS Records4 A records, 38 ms lookupPASS
| A | 52.222.132.104, 52.222.132.100, 52.222.132.89, 52.222.132.102 |
| AAAA | 2600:9000:201a:800:10:32d7:5200:93a1, 2600:9000:201a:2c00:10:32d7:5200:93a1, 2600:9000:201a:7000:10:32d7:5200:93a1, 2600:9000:201a:bc00:10:32d7:5200:93a1, 2600:9000:201a:e600:10:32d7:5200:93a1, 2600:9000:201a:d000:10:32d7:5200:93a1, 2600:9000:201a:6c00:10:32d7:5200:93a1, 2600:9000:201a:e800:10:32d7:5200:93a1 |
| CNAME | — |
| NS | ns-1966.awsdns-53.co.uk, ns-292.awsdns-36.com, ns-1205.awsdns-22.org, ns-1022.awsdns-63.net |
| MX | 1 aspmx.l.google.com 5 alt2.aspmx.l.google.com 5 alt1.aspmx.l.google.com 10 aspmx2.googlemail.com 10 aspmx3.googlemail.com |
| TXT | h1-domain-verification=dbqPB1RbBB8dKpav6behQHW6te9fqkgYxh5j6KBT8WvAYk4K anthropic-domain-verification-5e3gx1=w7e7qTKKuBeHvqq5pxF5hQwJG yahoo-verification-key=Y5pyDyRWbolgCA7dI+s6jK+TIzZ4Tlr0yKcLJ6TXaGA= intacct-esk=37636FD03564C14AE0638A86710AEC76 SPF v=spf1 include:metal._spf.discoursemail.com include:_spf.google.com include:amaz... 1password-site-verification=NALL2ULKKFFGTMZI2JGUTGBMHQ google-site-verification=fyWra9soC_wB9i_x1f1bLZ_u0shq84TdHC8ZHndxtHs google-site-verification=Pu_UqH5gBStNMnQ5aBXZAm1JNSNRua45Vwzb3vMdXfU |
| 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.
A+Redirect ChainNo redirects — direct accessPASS
https://discourse.org
9 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://discourse.org | 200 | 9 ms | HTTP/1.1 | AmazonS3 |
A+IPv6 ReadinessIPv6 reachable (1 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 87 URLsPASS
User-agent: *
Sitemap: https://www.discourse.org/sitemap.xml
A+Domain Intelligencediscourse.org — via Amazon Registrar, Inc., 24 years, 8 months oldPASS
151 days
December 10, 2026
214 days
Issued by Amazon
24 years, 8 months
Registered December 10, 2001
Not enabled
Protects against DNS spoofing
Unknown
2600:9000:201a:800:10:32d7:5200:93a1
Amazon Registrar, Inc.
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
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
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.
Learn more ▾ ▴
Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.
Source: ICANN / domain-security best practice