Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
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
BTLS Certificate Expiry & Recommendations32 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 Records1 A records, 27 ms lookupPASS
| A | 192.0.66.2 |
| AAAA | — |
| CNAME | — |
| NS | dns1.p05.nsone.net, dns4.p05.nsone.net, dns2.p05.nsone.net, dns3.p05.nsone.net |
| MX | — |
| TXT | google-site-verification=HPL8binrED5R9U3oyWqWsnVr1e2EI9hnKlLizQywIlQ |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.
Learn more ▾ ▴
Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.
Source: SRE practice / DNS architecture
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://github.blog
5 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://github.blog | 200 | 5 ms | HTTP/1.1 | nginx |
A+Crawlabilityrobots.txt present, sitemap with 17 URLsPASS
# START YOAST BLOCK
# ---------------------------
User-agent: *
Disallow:
Sitemap: https://github.blog/sitemap_index.xml
Sitemap: https://github.blog/de/sitemap_index.xml
Sitemap: https://github.blog/fr/sitemap_index.xml
# ---------------------------
# END YOAST BLOCK
- https://github.blog/post-sitemap.xml
- https://github.blog/post-sitemap2.xml
- https://github.blog/post-sitemap3.xml
- https://github.blog/post-sitemap4.xml
- https://github.blog/post-sitemap5.xml
- https://github.blog/page-sitemap.xml
- https://github.blog/changelog-sitemap.xm...
- https://github.blog/changelog-sitemap2.x...
- https://github.blog/changelog-sitemap3.x...
- https://github.blog/changelog-sitemap4.x...
- https://github.blog/category-sitemap.xml
- https://github.blog/post_tag-sitemap.xml
- https://github.blog/changelog-type-sitem...
- https://github.blog/changelog-label-site...
- https://github.blog/changelog-group-site...
- https://github.blog/recirculation_catego...
- https://github.blog/author-sitemap.xml
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencegithub.blog — via MarkMonitor, Inc (TLDs), 8 years old, hosted on WordPress.com (Automattic)PASS
336 days
May 17, 2027
32 days
Issued by Let's Encrypt
8 years
Registered May 17, 2018
Not enabled
Protects against DNS spoofing
WordPress.com (Automattic)
ASN AS2635
192.0.66.2
MarkMonitor, Inc (TLDs)
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