Is lexingtonlaw.com down or not working?

What happened to lexingtonlaw.com, why did the website go down and not work? Here you can see who else is having the same problem with lexingtonlaw.com, as well as possible solutions. According to our statistics, the following most often do not work: Website, Login, Account, Mobile App.

Current status: No failures

At the moment, according to our data, lexingtonlaw.com is working fine, but single failures are possible. If lexingtonlaw.com does not work for you, then report your problem and write a comment.
Add comment

What to do if the site lexingtonlaw.com is not available? Try our guide.

lexingtonlaw.com outage reports in the last 24 hours

lexingtonlaw.com - error and failure reports, troubleshooting methods

Leave your comment describing the failure and share with other users how to solve the problem.
  • No registration required.
  • Messages with obscene language and insults, as well as breaking the law, are not allowed to be published.
  • Active links in the text of the message are not published, but displayed in plain text.
  • It is forbidden to post your own and other people's personal data: addresses, phone numbers, emails, accounts in instant messengers, etc.

Technical information

Main page title:
lexingtonlaw.com
Protocol:
https
Status code:
401
Page size:
0.6 KB
Response time:
0.567sec.
IP:
151.101.2.133
Response headers:
connection: close
content-length: 586
content-type: text/html;charset=utf-8
server: DataDome
x-datadome: protected
accept-ch: Sec-CH-UA,Sec-CH-UA-Mobile,Sec-CH-UA-Platform,Sec-CH-UA-Arch,Sec-CH-UA-Full-Version-List,Sec-CH-UA-Model,Sec-CH-Device-Memory
charset: utf-8
cache-control: max-age=0, private, no-cache, no-store, must-revalidate
pragma: no-cache
access-control-allow-credentials: true
access-control-expose-headers: x-dd-b, x-set-cookie
access-control-allow-origin: http://lexingtonlaw.com
x-datadome-cid: AHrlqAAAAAMAcW8yFB_xxKAABS1HNg==
x-dd-b: 1
set-cookie: datadome=dWLflEXStJ3W14BEZnB84OWoqpLmAdhhjEs0C_MjWoonELdCYgH~Ek3DgF4vFuaNoswok6iMo2rwy_a15uDGpMphbFyxfTbUVC_tRvoecZcu6sKjgDEtwqpMYP3aKSSc; Max-Age=31536000; Domain=.lexingtonlaw.com; Path=/; Secure; SameSite=None
x-datadome-devicecheckpassed: NA
accept-ranges: bytes
date: Tue, 01 Oct 2024 09:41:29 GMT
via: 1.1 varnish
x-served-by: cache-ams2100121-AMS
x-cache: MISS
x-cache-hits: 0
x-timer: S1727775689.205720,VS0,VE11
strict-transport-security: max-age=31536000; includeSubDomains
DNS records:
A address151.101.130.133
ttl600
A address151.101.66.133
ttl600
A address151.101.2.133
ttl600
A address151.101.194.133
ttl600
MX exchangemxa-005df801.gslb.pphosted.com
priority10
MX exchangemxb-005df801.gslb.pphosted.com
priority10
NS valuens1.lexingtonlaw.com
NS valuens2.lexingtonlaw.com
TXT entriesgoogle-site-verification=CyCZrfKQ5Pz7zVdjchy1capEmHs1cwnvcUg0hY4q1Ow
TXT entriesgoogle-site-verification=5Y1q3bogOaSXegy6FPjahU532rL17DmuYWvlAM4B62w
TXT entriesMS=ms50048771
TXT entriesv=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com ~all
TXT entries_globalsign-domain-verification=nx5U56FiDUqhsckpguh1BWVo8oJVRsFtwCfGxdBN4e
TXT entriesZ+vzejMqZH6AAaSJ9sCHMN9nush3DTWGXGZk/CGsLm6wpi1HNW3lgsRv71++Uk6jLFLLbSYbkm01Wl4ZGUHNlw==
TXT entriesZOOM_verify_EzurT9SgSMuQZacYS3V9Lw
TXT entriesatlassian-domain-verification=HHplamBcFuMamrP/JJ9qkP5AiPteZaEQZLBOn7kQbglHF1voiI4lLPzF5zIPY27E
TXT entriesSendinblue-code:49d17941071946ca14cd72d4c34d74d7
TXT entriesgoogle-site-verification=E8DJLt34zooTMrfWj96KyIoeKIJ26BFc7B4RKAgfS6w
SOA nsnamens1.lexingtonlaw.com
hostmasterhostmaster.pgx.local
serial2013013405
refresh1200
retry600
expire1209600
minttl600

How to solve problems with lexingtonlaw.com

Errors on the lexingtonlaw.com website can be either on the server side or on your side (client side). If there is practically nothing to be done about errors on the server side (it remains only to wait for the site to work again), then with errors on the client side it is possible to solve the problem with the availability of lexingtonlaw.com on your own.