lexisnexis.com
Domduck has read lexisnexis.com on 6 days across 5 sources, since 2 August 2026. The domain was registered in 1997. Its robots.txt blocks 8 of the 8 AI crawlers Domduck tracks.
Last checked .
Charts appear once there are seven days of readings.
blocked
What changed
6 days of readings- 29 September 2026 (2026-09-29)
- robots.txt started returning HTTP 200 between 15 September 2026 and 29 September 2026, from 304.
- 15 September 2026 (2026-09-15)
- Nameservers changed between 31 August 2026 and 15 September 2026, from ns1.lexis-nexis.com, ns1.reedelsevier.com, ns2.lexisnexis.com, ns2.reedelsevier.com, ns3.lexisnexis.com, ns3.reedelsevier.com, ns4.lexisnexis.com to ns1.reedelsevier.com, ns2.reedelsevier.com, ns3.reedelsevier.com.
- robots.txt started returning HTTP 304 between 31 August 2026 and 15 September 2026, from 200.
- 31 August 2026 (2026-08-31)
- robots.txt started returning HTTP 200 between 17 August 2026 and 31 August 2026, from 304.
- 17 August 2026 (2026-08-17)
- Nameservers changed between 3 August 2026 and 17 August 2026, from ns1.lexis-nexis.com, ns2.lexisnexis.com, ns3.lexisnexis.com, ns4.lexisnexis.com to ns1.lexis-nexis.com, ns1.reedelsevier.com, ns2.lexisnexis.com, ns2.reedelsevier.com, ns3.lexisnexis.com, ns3.reedelsevier.com, ns4.lexisnexis.com.
- robots.txt started returning HTTP 304 between 3 August 2026 and 17 August 2026, from 200.
Popularity rank
72 days, lower is betterPosition in the Tranco list, a research ranking of the million most popular domains averaged over thirty days so a single day’s traffic spike cannot move it.
AI crawler policy
No llms.txt · Catch-all blocks every crawlerNo ChatGPT browsing or training
No ChatGPT search surface
No Claude retrieval
No Perplexity citation
Out of Gemini and AI Overviews grounding, Search ranking unaffected
Out of Apple Intelligence training
Out of most open training corpora
Out of TikTok and Doubao
Read from lexisnexis.com/robots.txt. “Not named” means the file says nothing about that agent, which is not the same as allowing it: a catch-all rule added later blocks it without anyone deciding to.
What the domain itself says
read directly, not from a vendor- Issuer
- GlobalSign nv-sa
- Valid
- Yes
- Expires
- 2026-12-13
- Protocol
- TLSv1.2
- Names covered
- 4
- A records
- 1
- AAAA records
- 0
- Mail exchangers
- 1
- Nameservers
- ns1.reedelsevier.com, ns2.reedelsevier.com, ns3.reedelsevier.com
- DMARC policy
- reject
- Registered
- 1997-06-26
- Registrar
- MarkMonitor Inc.
- Registry status
- client delete prohibited, client transfer prohibited, client update prohibited
How lexisnexis.com compares to other .com domains
Questions
- Does lexisnexis.com block GPTBot?
- Yes. lexisnexis.com's robots.txt disallows GPTBot through a catch-all rule.
- Does lexisnexis.com publish an llms.txt file?
- No. Domduck found no llms.txt at lexisnexis.com.
- When was lexisnexis.com registered?
- 26 June 1997, through MarkMonitor Inc..
- Who issues lexisnexis.com's certificate?
- GlobalSign nv-sa.
How this page is made
Every number on this page is a measurement Domduck took itself or read from a public source, on a stated date. Nothing here is written by a language model. Where a value has not changed, no sentence is generated about it.
First reading . 5 sources, 6 days with at least one reading. The popularity rank comes from the Tranco list; the registration record from RDAP, which ICANN requires registries to publish. The certificate, the DNS records and the crawler policy are read by Domduck directly from lexisnexis.com.