Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BCrawlabilityno robots.txt, no sitemapREVIEW
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.
Learn more ▾ ▴
A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.
Source: robotstxt.org
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
No robots.txt found
This is fine for most sites — a missing robots.txt allows all crawling by default.
No sitemap found
Adding a sitemap helps search engines discover your pages.
BTLS Certificate Expiry & Recommendations280 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
BCDN & DeliveryAkamaiREVIEW
A+DNS Records1 A records, 66 ms lookupPASS
| A | 184.24.166.61 |
| AAAA | 2a02:26f0:1180:183::e96, 2a02:26f0:1180:19a::e96 |
| CNAME | — |
| NS | dns4.p01.nsone.net, dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net |
| MX | 0 bedbathandbeyond-com.mail.protection.outlook.com |
| TXT | google-site-verification=0shOleXMq9Sn_MozjJa0IxedphTm9K1EOcLlqhR6434 google-site-verification=rvXDdWoFYWhxfHUjT0Mj9CtO9VPyowlql70D0InpC5M apple-domain-verification=VTh1xZZrcQBANbGG google-site-verification=Gp7vx2DK9x3whQzhsHAV4eayFaAlrwUMA_8OTwcbEcg MS=ms38501519 google-site-verification=uIvKnhWZYMGr2UwELrrhCZeeAwcxLevI8Ad5037PCEA SPF v=spf1 ip4:65.116.112.0/21 ip4:173.241.144.0/20 ip4:52.8.140.255 ip4:54.164.132.... google-site-verification=S9ZXx5JpJ-BkNzRKppT9xpFUe5ZsN58-sYz7vBAJLAM |
| 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.
ARedirect Chain1 redirect(s), 159 ms totalPASS
https://bedbathandbeyond.com
100 ms · HTTP/1.1
https://www.bedbathandbeyond.com/
59 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://bedbathandbeyond.com | 301 | 100 ms | HTTP/1.1 | AkamaiGHost |
| 2 | https://www.bedbathandbeyond.com/ | 403 | 59 ms | HTTP/1.1 | AkamaiGHost |
See the visual redirect chain in the HTTP Probe tab →
A+IPv6 ReadinessIPv6 reachable (140 ms)PASS
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencebedbathandbeyond.com — via MarkMonitor Inc., 29 years, 10 months oldPASS
857 days
November 16, 2028
280 days
Issued by DigiCert Inc
29 years, 10 months
Registered November 17, 1996
Not enabled
Protects against DNS spoofing
Unknown
2a02:26f0:1180:19a::e96
MarkMonitor 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