Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BCrawlabilityrobots.txt present, sitemap with 2229 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
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
BTLS Certificate Expiry & Recommendations197 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
Recommended actions
- 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
A+DNS Records4 A records, 41 ms lookupPASS
| A | 52.84.174.104, 52.84.174.48, 52.84.174.73, 52.84.174.126 |
| AAAA | — |
| CNAME | — |
| NS | ns-1497.awsdns-59.org, ns-269.awsdns-33.com, ns-1652.awsdns-14.co.uk, ns-678.awsdns-20.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 | MS=ms84680364 1password-site-verification=TPIIQMLIDNFZVKFU4KF3R72LRM pardot1121843=294f355dc244184aa79a9d92d7e82dbe6b4e3486bb2b74be1cabe0af2b14981d google-site-verification=LPH506ckn9ILnoLbU7-_iLGwb7KnC-whH6LDFsYpvso SPF v=spf1 include:amazonses.com include:_spf.google.com include:mail.zendesk.com in... d1l2ndf1rv58my.cloudfront.net google-site-verification=MEP5IUpWIF4sLlOnOyFoy8IB9KA-aZmKBukf30eO4-Y facebook-domain-verification=wvqcv3rz5jjrhuaoeyedkmqtyugi7b bugcrowd-verification=4e328e2cf7e9d86a17f10faeceeedd3e google-site-verification=rlD0fAw4zex4U4XrrJn3Zf--QddLebZcb5seIznZ1_4 atlassian-domain-verification=OTixRADMse89Mpeybwy2m81PhC7hgIimN7beU8xwqsKK6TjWxi... t9dtxv28tq4n7tbn7355t26r62jtyh19 sending_domain1121843=909326644e56ca9f0d77cbc24cd152887da893af83565426791cae05db... google-site-verification=-E_rSfU2SJ037l6KuAS1LMH7BQ7Lw-Feb1I7JZvVpqI google-site-verification=nD5EO832vd1LtEqVpphjLkH_nV4gxUKQb7MRotRUUkY |
| 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.
ARedirect Chain1 redirect(s), 214 ms totalPASS
https://code.org
57 ms · HTTP/1.1
https://code.org/en-US
157 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://code.org | 307 | 57 ms | HTTP/1.1 | CloudFront |
| 2 | https://code.org/en-US | 200 | 157 ms | HTTP/1.1 | CloudFront |
See the visual redirect chain in the HTTP Probe tab →
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencecode.org — via Amazon Registrar, Inc., 26 years, 11 months old, hosted on AWSPASS
106 days
September 28, 2026
197 days
Issued by Amazon
26 years, 11 months
Registered September 28, 1999
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
52.84.174.104
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