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
Preferred variant: non-www
HTTP → HTTPS
HTTP version does not redirect to HTTPS
BTLS Certificate Expiry & Recommendations61 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
A+DNS Records4 A records, 39 ms lookupPASS
| A | 185.199.111.153, 185.199.109.153, 185.199.108.153, 185.199.110.153 |
| AAAA | 2606:50c0:8001::153, 2606:50c0:8000::153, 2606:50c0:8002::153, 2606:50c0:8003::153 |
| CNAME | — |
| NS | dahlia.ns.cloudflare.com, earl.ns.cloudflare.com |
| MX | 10 mxb.mailgun.org 10 mxa.mailgun.org |
| TXT | SPF v=spf1 include:spf.messagingengine.com include:mailgun.org include:_hostedspf.di... |
| 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://jekyllrb.com
6 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://jekyllrb.com | 200 | 6 ms | HTTP/1.1 | GitHub.com |
A+IPv6 ReadinessIPv6 reachable (0 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 210 URLsPASS
Sitemap: https://jekyllrb.com/sitemap.xml
A+Domain Intelligencejekyllrb.com — via NameCheap, Inc., 17 years, 2 months oldPASS
316 days
April 28, 2027
61 days
Issued by Let's Encrypt
17 years, 2 months
Registered April 28, 2009
Not enabled
Protects against DNS spoofing
Unknown
2606:50c0:8002::153
NameCheap, 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