Skip to content
https://lexology.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
80
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Santa Clara, United States
302 Found
Checks
9
5 PASS 3 REVIEW 1 FIX
F
IPv6 Readiness
Action
IPv6 records exist but unreachable
FIX
IPv6 records exist but unreachable
Warning::
IPv6 DNS records exist but server is not reachable
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Got: 2606:4700::6812:d66, 2606:4700::6812:c66
Info::
IPv6 connection error
Got: dial tcp6 [2606:4700::6812:d66]:443: connect: network is unreachable
IPv6 Misconfigured
AAAA Records 2606:4700::6812:d66, 2606:4700::6812:c66 Connection UNREACHABLE

Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.

Why this matters

Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.

Learn more ▾

Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.

Source: RFC 8305 (Happy Eyeballs)

C
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.lexology.com/
200https://lexology.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://lexology.com/ → https://www.lexology.com/

Use 301 (permanent) instead of 302 (temporary)

B
TLS Certificate Expiry & Recommendations
74 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

74
days left
0d 30d 60d 90d+

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
B
CDN & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: SJC)
Got: cf-ray: 9f00799c7bb5dc9b-SJC
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9f00799c7bb5dc9b-SJC
A+
DNS Records
2 A records, 9 ms lookup
PASS
2 A records, 9 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.18.13.102, 104.18.12.102
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700::6812:d66, 2606:4700::6812:c66
Info::
2 nameserver(s) configured
Got: lila.ns.cloudflare.com, tom.ns.cloudflare.com
Info::
2 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 9 ms
Got: 9 ms
A104.18.13.102, 104.18.12.102
AAAA2606:4700::6812:d66, 2606:4700::6812:c66
CNAME—
NSlila.ns.cloudflare.com, tom.ns.cloudflare.com
MX
10 eu-smtp-inbound-1.mimecast.com
10 eu-smtp-inbound-2.mimecast.com
TXT
DMqisHGjDoswlVHw3MUerimftHdgl4NNQAS8Sh9Ap7gQogREgJBFwVycWAOftOcFegtqGmqqU7mwVsRX...
MS=ms40750952
google-site-verification=pb_eAdiZt9K4Z2HuFFXItlRuOKt1mgnPwrXZIRkTEgw
pardot878412=c4bdc73523c7163dcb1392d4f248bba615457dd9a20c2c59b976f0ad0a759f69
SPF v=spf1 include:spf.protection.outlook.com include:eu._netblocks.mimecast.com inc...
CAALookup not available with standard resolver
Resolved in 9 ms

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A
Redirect Chain
1 redirect(s), 510 ms total
PASS
1 redirect(s), 510 ms total
Info::
Single redirect
Got: https://lexology.com → https://www.lexology.com/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://lexology.com
Info::
Redirect overhead: 510 ms total
Got: 510 ms

https://lexology.com

26 ms · HTTP/1.1

302

https://www.lexology.com/

483 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://lexology.com30226 msHTTP/1.1cloudflare
2https://www.lexology.com/200483 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

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

A+
Crawlability
robots.txt present, sitemap with 187 URLs
PASS
robots.txt present, sitemap with 187 URLs
Info::
robots.txt is present
Got: 1947 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 187 entries
Info::
Sitemap index with 187 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1947 B Sitemaps referenced 1 User-agents magpie-crawler, peer39_crawler, AwarioSmartBot, Omgilibot, Omgili, FacebookBot, Bytespider, DataForSeoBot, peer39_crawler/1.0, PerplexityBot, *, CCBot, Amazonbot, anthropic-ai, ClaudeBot, Claude-Web, ChatGPT-User, Google-Extended, AwarioRssBot, cohere-ai Blocking No — crawling allowed
User-agent: GPTBot
Disallow: /


User-agent: CCBot

Disallow: /


User-agent: ChatGPT-User

Disallow: /


User-agent: Google-Extended

Disallow: /


User-agent: Omgilibot

Disallow: /


User-agent: Omgili

Disallow: /


User-agent: FacebookBot

Disallow: /


User-agent: Bytespider

Disallow: /


User-agent: Amazonbot

Disallow: /


User-agent: anthropic-ai

Disallow: /


User-agent: AwarioRssBot

Disallow: /


User-agent: AwarioSmartBot

Disallow: /


User-agent: ClaudeBot

Disallow: /


User-agent: Claude-Web

Disallow: /


User-agent: cohere-ai

Disallow: /


User-agent: DataForSeoBot

Disallow: /


User-agent: magpie-crawler

Disallow: /


User-agent: peer39_crawler

Disallow: /


User-agent: peer39_crawler/1.0

Disallow: /


User-agent: PerplexityBot

Disallow: /


User-agent: *

Allow: /

Disallow: /Admin

Disallow: /admin

Disallow: /Account

Disallow: /account

Disallow: /Library/Document.ashx

Disallow: /library/Document.ashx

Disallow: /Library/document.ashx

Disallow: /library/document.ashx

Disallow: /Library/ReadItLaterPopup.aspx

Disallow: /library/ReadItLaterPopup.aspx

Disallow: /r.ashx

Disallow: /R.ashx

Disallow: /r.ashx?i=*

Disallow: /R.ashx?i=*

Disallow: /r.ashx?l=*

Disallow: /R.ashx?l=*

Disallow: /(X(1

Disallow: /(x(1

Disallow: /library/forward.aspx

Disallow: /library/account/

Disallow: /library/firms/

Disallow: /library/images/

Disallow: /emailv_v2

Disallow: /Emailv_v2

Disallow: /newsfeedemail

Disallow: /olddefault.aspx

Disallow: /OldDefault.aspx

Disallow: /oldDefault.aspx

Disallow: /Olddefault.aspx

Disallow: /Track

Disallow: /track

Disallow: /r/

Disallow: /R/

Disallow: /email/r/

Disallow: /Email/R/

Disallow: /email/R/

Disallow: /Email/r/

Allow: /Account/Register.aspx

Allow: /Account/register.aspx

Allow: /account/Register.aspx

Allow: /account/register.aspx

Allow: /account/rsscontrolpanel.aspx

Sitemap: https://www.lexology.com/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 187 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
lexology.com — via Cloudflare, Inc., 29 years, 1 months old, hosted on Cloudflare
PASS
lexology.com — via Cloudflare, Inc., 29 years, 1 months old, hosted on Cloudflare
Info::
Domain registered until Aug 20, 2026 (4 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: Cloudflare, Inc.
Warning::
Registrar lock is NOT enabled
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.
Info::
Hosting: Cloudflare
Got: AS13335
Domain expiry

67 days

August 20, 2026

SSL certificate

74 days

Issued by Google Trust Services

Domain age

29 years, 1 months

Registered August 21, 1997

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

104.18.12.102

Registrar

Cloudflare, Inc.

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Cloudflare, Inc.
Created August 21, 1997 (29 years, 1 months ago)
Expires August 20, 2026 (4 months)
Last Updated July 21, 2025
Name Servers lila.ns.cloudflare.com, tom.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 104.18.12.102
ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)
Provider Cloudflare
Data source: rdap (0.2s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

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.

Why this matters

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

A+
HTTP Probe Timing
Total 31 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
9 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
3 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
10 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
31 ms
Total Time Total request time from DNS lookup through full response.
31 ms

Connection waterfall

DNS Lookup 9 ms TCP Connect 3 ms TLS Handshake 10 ms Server Processing 9 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback