Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCrawlabilityActionrobots.txt present, no sitemapFIX
Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.
Disallow: / in robots.txt blocks every search crawler — the site becomes invisible in organic search.
Learn more ▾ ▴
Common deployment mistake: a staging robots.txt with `User-agent: * / Disallow: /` ships to prod. The site falls out of search results within days. Verify your robots.txt is the production-intended version. If this is intentional (private site), no action needed.
Source: Google Search Central
A sitemap helps search engines discover and index your pages more efficiently.
No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.
Learn more ▾ ▴
A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.
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
User-agent: OAI-SearchBot
User-agent: GPTBot
Disallow: /
User-agent: ChatGPT-User
Crawl-delay: 2
User-agent: Googlebot
User-agent: Google
User-agent: Mediapartners-Google
User-agent: bingbot
User-agent: bing
User-agent: msnbot
User-agent: msn
User-agent: Slurp
User-agent: Yandex
User-agent: Facebot
User-agent: Twitterbot
User-agent: ia_archiver
User-agent: naver
User-agent: NaverBot
User-agent: Yeti
Disallow: /login
Disallow: /_api/
Disallow: /admin/
Disallow: /webdesigners
Disallow: /Cargo-Webdesign-Directory
Crawl-delay: 2
User-agent: *
Disallow: /
No sitemap found
Adding a sitemap helps search engines discover your pages.
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 & Recommendations294 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
Recommended actions
- Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
- 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 Records2 A records, 38 ms lookupPASS
| A | 34.232.168.74, 52.23.18.66 |
| AAAA | — |
| CNAME | — |
| NS | ns-660.awsdns-18.net, ns-1229.awsdns-25.org, ns-184.awsdns-23.com, ns-1996.awsdns-57.co.uk |
| MX | 10 mx1.emailsrvr.com 20 mx2.emailsrvr.com |
| TXT | google-site-verification=bcBS4YranTaAZVF490BZrZxc40-CdBLBft74SxZ_Sxo SPF v=spf1 ip4:64.49.217.119 ip4:64.49.217.117 ip4:64.49.217.116 ip4:64.49.217.118 a... facebook-domain-verification=xhn4dzr9agutlpm8ilphherijydjx3 SPF v=spf1 include:emailsrvr.com ~all |
| 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), 836 ms totalPASS
https://cargocollective.com
394 ms · HTTP/1.1
https://cargo.site
442 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://cargocollective.com | 302 | 394 ms | HTTP/1.1 | Apache |
| 2 | https://cargo.site | 200 | 442 ms | HTTP/1.1 | cargo-router |
See the visual redirect chain in the HTTP Probe tab →
If permanent, use 301 instead.
302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.
Learn more ▾ ▴
Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).
Source: Google Search Central
AURL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Use 301 (permanent) instead of 302 (temporary)
A+Domain Intelligencecargocollective.com — via Tucows Domains Inc., 17 years, 5 months old, hosted on AWSPASS
216 days
February 12, 2027
294 days
Issued by Amazon
17 years, 5 months
Registered February 12, 2009
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
34.232.168.74
Tucows Domains 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