Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DRedirect ChainAction3 redirect(s), 326 ms totalFIX
https://bloomberglaw.com
33 ms · HTTP/1.1
https://www.bloomberglaw.com/
68 ms · HTTP/1.1
https://wsauth.bloombergindustry.com/wsa...
131 ms · HTTP/1.1
https://www.bloomberglaw.com/login?targe...
94 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://bloomberglaw.com | 301 | 33 ms | HTTP/1.1 | Apache |
| 2 | https://www.bloomberglaw.com/ | 302 | 68 ms | HTTP/1.1 | Apache |
| 3 | https://wsauth.bloombergindustry.com/wsa... | 302 | 131 ms | HTTP/1.1 | |
| 4 | https://www.bloomberglaw.com/login?targe... | 200 | 94 ms | HTTP/1.1 | Apache |
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
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
CCrawlabilityActionrobots.txt present, sitemap with 9223 URLsREVIEW
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
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: Googlebot
Allow: /
User-agent: Google-InspectionTool
Allow: /
User-agent: Bingbot
Allow: /
User-agent: BingPreview
Allow: /
User-agent: *
Disallow: /
BTLS Certificate Expiry & Recommendations204 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- 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
A+DNS Records2 A records, 5 ms lookupPASS
| A | 69.187.32.73, 69.191.136.73 |
| AAAA | — |
| CNAME | — |
| NS | dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net, pdns1.ultradns.net, pdns3.ultradns.org, pdns5.ultradns.info |
| MX | 0 mgcnj2.bloomberg.com 0 mgcny1.bloomberg.com 0 mgcnj1.bloomberg.com 0 mgcny2.bloomberg.com |
| TXT | MS=ms19028638 openai-domain-verification=dv-DUUJtFhhcle5WtSKhPZFXgZq miro-verification=46ac7c8ffa0db9d972c2a10f3775e34d4ffe7f92 ciscocidomainverification=6d112b9ca9f8c3d132ecccf9720301894bd7e06488bbf2a61ba6c4... atlassian-domain-verification=iOrMXSk9ej2nB0JEW7KdEw+C3wMPhmtlYFff2SQJx7wwy14ESS... SPF v=spf1 include:spf.bna.com include:spf.protection.outlook.com include:_spf.sales... |
| 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.
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 Intelligencebloomberglaw.com — via CSC Corporate Domains, Inc., 26 years, 2 months old, hosted on BLOOMBERG-NET - Bloomberg, LP, USPASS
EXPIRED
June 13, 2026
204 days
Issued by DigiCert Inc
26 years, 2 months
Registered June 13, 2000
Not enabled
Protects against DNS spoofing
BLOOMBERG-NET - Bloomberg, LP, US
ASN AS10361
69.187.32.73
CSC Corporate Domains, Inc.
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