Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.FRedirect ChainAction3 redirect(s), 1828 ms totalFIX
https://allaboutbirds.org
474 ms · HTTP/1.1
https://www.allaboutbirds.org/
666 ms · HTTP/1.1
http://www.allaboutbirds.org/news/
234 ms · HTTP/1.1
https://www.allaboutbirds.org/news/
453 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://allaboutbirds.org | 301 | 474 ms | HTTP/1.1 | cloudflare |
| 2 | https://www.allaboutbirds.org/ | 301 | 666 ms | HTTP/1.1 | cloudflare |
| 3 | http://www.allaboutbirds.org/news/ | 301 | 234 ms | HTTP/1.1 | cloudflare |
| 4 | https://www.allaboutbirds.org/news/ | 200 | 453 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
Each redirect adds latency. Try to minimize the chain to 1 hop.
Redirect chain — each hop adds latency; combine into one redirect where possible.
Source: Google Search Central / web.dev
Redirect directly from https://allaboutbirds.org to https://www.allaboutbirds.org/news/
Redirect chain could be flattened to one hop — server config tweak removes intermediate latency.
Source: web.dev
CCrawlabilityActionrobots.txt present, sitemap with 0 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
An empty sitemap provides no value. Add <url> entries for your pages.
An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.
Learn more ▾ ▴
Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.
Source: Google Search Central / sitemaps.org
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
User-agent: *
Disallow: /wp-admin/
Disallow: /stagingguide/
Disallow: /guide/*/media-browser-overview/
Disallow: /guide/noindex/
Disallow: /guide/noindex/photo/*.jpg$
Disallow: /guide/noindex/photo/*.png$
Crawl-delay: 5
User-agent: AhrefsBot
Disallow: /
User-agent: Googlebot-Image
Disallow: /guide/noindex/photo/*.jpg$
Disallow: /guide/noindex/photo/*.png$
Disallow: /guide/noindex/*.jpg$
Disallow: /guide/noindex/*.png$
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 & Recommendations32 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 Records3 A records, 45 ms lookupPASS
| A | 172.67.69.67, 104.26.0.144, 104.26.1.144 |
| AAAA | 2606:4700:20::681a:190, 2606:4700:20::ac43:4543, 2606:4700:20::681a:90 |
| CNAME | — |
| NS | isla.ns.cloudflare.com, ian.ns.cloudflare.com |
| MX | 0 smtp.secureserver.net 10 mailstore1.secureserver.net |
| TXT | google-site-verification=kQ2_WDGjVTgXkG_Rw6ILmZyn8V400Ss3kcy_EXjzmec google-site-verification=7lDeEXgqCfXOw1igXBCDRvlg-XiS5rn3jEhJkHcl0-c SPF v=spf1 include:servers.mcsv.net ?all facebook-domain-verification=vhnwfplzpxlt853b6c8qd3q9xtvc1i google-site-verification=HpDCDvQxPmJJ9tJTPayy0l9yhnRyeMHXdtIvc9fv7Fc lr7lfnewpp7sewm2s5hr |
| 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+IPv6 ReadinessIPv6 reachable (16 ms)PASS
A+Domain Intelligenceallaboutbirds.org — via GoDaddy.com, LLC, 21 years, 4 months oldPASS
649 days
March 23, 2028
32 days
Issued by Google Trust Services
21 years, 4 months
Registered March 23, 2005
Not enabled
Protects against DNS spoofing
Unknown
2606:4700:20::681a:90
GoDaddy.com, LLC
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