Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DRedirect ChainAction3 redirect(s), 238 ms totalFIX
https://bcorporation.net
38 ms · HTTP/1.1
https://www.bcorporation.net/
60 ms · HTTP/1.1
https://www.bcorporation.net/en-us
34 ms · HTTP/1.1
https://www.bcorporation.net/en-us/
106 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://bcorporation.net | 308 | 38 ms | HTTP/1.1 | Vercel |
| 2 | https://www.bcorporation.net/ | 302 | 60 ms | HTTP/1.1 | Vercel |
| 3 | https://www.bcorporation.net/en-us | 308 | 34 ms | HTTP/1.1 | Vercel |
| 4 | https://www.bcorporation.net/en-us/ | 200 | 106 ms | HTTP/1.1 | Vercel |
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
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
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
BCrawlabilityrobots.txt present, sitemap with 19983 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
User-Agent: *
Allow: /
Host: https://www.bcorporation.net/
Sitemap: https://www.bcorporation.net//sitemap.xml
BTLS Certificate Expiry & Recommendations85 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 & DeliveryVercelREVIEW
A+DNS Records1 A records, 9 ms lookupPASS
| A | 76.76.21.21 |
| AAAA | — |
| CNAME | — |
| NS | ns-1379.awsdns-44.org, ns-1745.awsdns-26.co.uk, ns-72.awsdns-09.com, ns-849.awsdns-42.net |
| MX | 1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 alt4.aspmx.l.google.com 10 alt3.aspmx.l.google.com |
| TXT | 00D80000000a057=1TBNx000000021w 1f3wp13l4llq8csvc8blglqx8yhbmphd 24AB664EC0 apple-domain-verification=ZPVcXXxGhQon5SGF asv=5a69e013f871b6d6228f7ad992e629ca atlassian-domain-verification=IUOnEGCbGgRbMtG2MopZjbUnwWK39iMc6UuqQyJFTPEx6YmlMe... google-site-verification=biFvkCYadaBwrXsGsc2rei_ZXCbd9VA2G6xPeyc7pRY google-site-verification=oREVCBDNVJnv0tG2UfETmJHU_Dsbyn8Osl1NGF1LOy8 miro-verification=58007d211a421cd6e5da1c158ee834334d12961b pardot39792=ca5aa5a57e7b4034aaa29d662a194972d475c55c5b4eb6b11f917fea9e6ebc32 SPF v=spf1 +a +mx +ip4:204.44.192.74 +include:_spf.google.com +include:aspmx.pardot.... |
| 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.
AURL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Use 301 (permanent) instead of 302 (temporary)
ADomain Intelligencebcorporation.net — via eNom, LLC, 21 years old, hosted on AWSPASS
EXPIRED
July 11, 2026
85 days
Issued by Let's Encrypt
21 years
Registered July 11, 2005
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
76.76.21.21
eNom, LLC
Expiry timeline
Recommended actions
- Domain has EXPIRED — renew immediately to avoid total site outage
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Consider enabling auto-renewal to prevent accidental expiration.
Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.
Source: ICANN renewal policy
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