Skip to content
https://lexisnexis.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
77
GRADE
C
FIX
2
REVIEW
2
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 2 REVIEW 2 FIX
D
Crawlability
Action
robots.txt present, no sitemap
FIX
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 40 bytes
Critical::
robots.txt blocks all crawlers
Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.

Why this matters

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.

Why this matters

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.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 40 B Sitemaps referenced 0 User-agents * Blocking Yes — all crawlers blocked
User-agent: *


Disallow: /

Noindex: /
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

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

Certificate validity

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

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 Records
1 A records, 650 ms lookup
PASS
1 A records, 650 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 138.12.4.174
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns3.lexisnexis.com, ns2.lexisnexis.com, ns4.lexisnexis.com, ns1.lexis-nexis.com
Info::
1 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
Warning::
DNS resolution is slow (650 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 650 ms
A138.12.4.174
AAAA
CNAME
NSns3.lexisnexis.com, ns2.lexisnexis.com, ns4.lexisnexis.com, ns1.lexis-nexis.com
MX
10 lexisnexis-com.mail.protection.outlook.com
TXT
onetrust-domain-verification=1d24ebf1576b4466add8b2f781d3d902
webexdomainverification.=98455431-ecca-47f7-b74c-db6f39e5df0c
apple-domain-verification=kq0qmtQYbGFhbCNe
_ucaj3hzrowyadogalc9an52dnqorzyb
adobe-idp-site-verification=fd4fae74b683e6e22ef9b491871ae9f0faf7856b8a8588d267e2...
facebook-domain-verification=g6cmq4oko64h1gjhy7dkniag7ku5kb
fastly-domain-delegation-dd439187-11102021
google-site-verification=rcdQIw9Aqm7sYGK3OX5TRkiJiJ5ZRtc-rqyDpow65uY
pardot899741=7fad9f59001d1b63f99cb7c30d03cf4e993362b26290e1e703844b83fd324a03
AXw1tdfIuU9b7b6NhpHgxVt4wvmtCYcuWENPieRrGx0=
pardot899751=ac79bfb84cd1fdf91244ff3b8b24b5bd04e57ac936f730451348d8432d78686c
onetrust-domain-verification=843d879653584ea7b545ef842cd13b11
cisco-ci-domain-verification=2d7c39a7c233dcaf1174882db640ffa59e579e5375d2d00a38e...
pardot899741=4d6a245a8421164ff6507db4fd629bc9060ee465dd2f10952fdb30a91e0380fc
pardot899741=7813ebaeb3c147a17b7e00d5a8af4b6a480ba23567bb6fa37fd055e556494a03
VvfeQSRIsxT4RrK4Z8xwBoF4dny2TAKc3uBogPZh911sXexDIEF3iK4zy4mVzexj9pQTvmkqzvlvGxMJ...
google-site-verification=JUSVSgKctH4TF38tZyDPNmZ8QxJ0zmUgov2sriW3a0I
pardot1028433=19772e49dc233e068d316ff928c45f12f0d2285a064ba1b29dd7b0963090ab7b
webexdomainverification.=9094f915-21e5-4e23-96f0-7cd5b236311d
SPF v=spf1 exists:%{i}._i.%{d}._d.espf.agari.com include:%{d}.33.spf-protect.agari.c...
pardot1020222=aa23dbd3c0ee77708b9ae8a89d4517df7b9f1e6fee42bf7177b78f13e02c52cd
pardot1020222=f6855c0731bacfc5774557f856213f2b93ef23c085d8ffd9c681960e5028219b
google-gws-recovery-domain-verification=64642360
pardot899741=5bea8ec8215073c65f9365fef8b5aed7b97eb32215d3bba8155758c7b5554846
smartsheet-site-validation=socDQWpHCnktSj6-goC2CPywT68XkmU6
anthropic-domain-verification-jh44hw=jzyG4ohMTmk7jUNz5SdtMdWyH
sending_domain1020222=1bc5e9bddf90f68f8cb3492c962733d87d72066ec6e9a0b3e4e59ecccb...
sending_domain1028433=55066e08e19adcc207f5f3027c3804bb0a2d7f9f1dd68e81cf8d7fd5ae...
pardot682313=c2a8d9dbaa032dca9785a38893ee3e0563f2227e1214fa94e155928cbe00b2ac
webexdomainverification.=10016647-2f54-4099-b985-db46b7f811bc
figma-domain-verification=7e9fc71b9c170bbc3d49380395182fb0a28e13607a352e108abb89...
pardot1079963=5850afdb4436e3ad368e33be5e8834a6663091964b43d12b69178d13487f37b2
MS=ms99617937
canva-site-verification=OLO5hngordp0CTr-RvwC5A
zapier-domain-verification-challenge=f8dae159-fc12-442e-87f6-be02edac0f63
_ene816jlthyl0j6udwog3148m255lp2
pardot1020222=e7958620038f304fedff0327e58b7ce8f3fabbee6ba642f8d39ca1c60af86187
ZOOM_verify_uE8UJePvRJuQ1Pc8Z0tVj0
pendo-domain-verification=NyDyUaV2ESqQWAgvRjhIsnDkFeM
pardot682313=a55158ece703897aaa0a119379e16003cdfa45ad3c87d2cb1f1b2dd3a3e4f017
pardot_200072_*=bd0fbecef50fc865c4efdb681fd569834d66927be682bfc5e8b11125ff462a53
zapier-domain-verification-challenge=04b7fdf3-37d3-4340-8136-491dbf7ea242
slack-domain-verification=6Fs5lrs127t66165SRX4kKaQlKpbQry9cVsZpSbp
pardot1020222=43739bc9a9522d742aa6e31ac4646061774f58f19740ffc6e4a6f38261a8ed4c
pardot200072=8bbbddef393795c0b367eaa8556582b8483ae4a4fc56c090c00b03721934a069
miro-verification=39a0a4ee76533d3eb6ef3701caa0a7817f8d3390
pardot_322251_*=afc209af3ea666b0b8da5d0527d49c4e74dc2b37e4800df77b096360b4396e47
webexdomainverification.=0b066749-67a2-41d5-b483-5bc225de67e1
pardot1020222=2ac5e6b5488fa603b8d462ab32278b251ca2607fab6fe29155ef599e0e6ed7d1
CAALookup not available with standard resolver
Resolved in 650 ms

Multiple A records provide failover if one server goes down.

Why this matters

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.

Why this matters

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

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A
Redirect Chain
1 redirect(s), 528 ms total
PASS
1 redirect(s), 528 ms total
Info::
Single redirect
Got: https://lexisnexis.com → https://www.lexisnexis.com/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 528 ms total
Got: 528 ms

https://lexisnexis.com

493 ms · HTTP/1.1

301

https://www.lexisnexis.com/

35 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://lexisnexis.com301493 msHTTP/1.1www.lexisnexis.com 9999
2https://www.lexisnexis.com/40335 msHTTP/1.1CloudFront

See the visual redirect chain in the HTTP Probe tab →

A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

403https://www.lexisnexis.com/
200https://lexisnexis.com/

HTTP → HTTPS

301http://lexisnexis.com/ https://www.lexisnexis.com/

Consistent

A
Domain Intelligence
lexisnexis.com — via MarkMonitor Inc., 29 years, 2 months old, hosted on LEXIS2-AS - RELX inc., US
PASS
lexisnexis.com — via MarkMonitor Inc., 29 years, 2 months old, hosted on LEXIS2-AS - RELX inc., US
Warning::
Domain expires in 64 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jun 25, 2026
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: MarkMonitor 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: LEXIS2-AS - RELX inc., US
Got: AS32472
Domain expiry

9 days

June 25, 2026

SSL certificate

66 days

Issued by GlobalSign nv-sa

Domain age

29 years, 2 months

Registered June 26, 1997

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

LEXIS2-AS - RELX inc., US

ASN AS32472

138.12.4.174

Registrar

MarkMonitor Inc.

Unlocked 4 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 MarkMonitor Inc.
Created June 26, 1997 (29 years, 2 months ago)
Expires June 25, 2026 (2 months)
Last Updated May 24, 2025
Name Servers ns1.lexis-nexis.com, ns2.lexisnexis.com, ns3.lexisnexis.com, ns4.lexisnexis.com
DNSSEC Not enabled
Hosting
IP Address 138.12.4.174
ASN AS32472 (LEXIS2-AS - RELX inc., US)
Provider LEXIS2-AS - RELX inc., US
Data source: rdap (0.4s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

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.

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 570 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
123 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
109 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
222 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
570 ms
Total Time Total request time from DNS lookup through full response.
570 ms

Connection waterfall

DNS Lookup 123 ms TCP Connect 109 ms TLS Handshake 222 ms Server Processing 117 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