Is li.me down or not working?

What happened to li.me, why did the website go down and not work? Here you can see who else is having the same problem with li.me, 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, li.me is working fine, but single failures are possible. If li.me does not work for you, then report your problem and write a comment.
Add comment

What to do if the site li.me is not available? Try our guide.

li.me outage reports in the last 24 hours

li.me - 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:
Just a moment...
Protocol:
https
Status code:
403
Page size:
9.3 KB
Response time:
0.395sec.
IP:
15.197.198.30
Response headers:
date: Tue, 01 Oct 2024 03:20:51 GMT
content-type: text/html; charset=UTF-8
content-length: 9557
connection: close
accept-ch: Sec-CH-UA-Bitness, Sec-CH-UA-Arch, Sec-CH-UA-Full-Version, Sec-CH-UA-Mobile, Sec-CH-UA-Model, Sec-CH-UA-Platform-Version, Sec-CH-UA-Full-Version-List, Sec-CH-UA-Platform, Sec-CH-UA, UA-Bitness, UA-Arch, UA-Full-Version, UA-Mobile, UA-Model, UA-Platform-Version, UA-Platform, UA
critical-ch: Sec-CH-UA-Bitness, Sec-CH-UA-Arch, Sec-CH-UA-Full-Version, Sec-CH-UA-Mobile, Sec-CH-UA-Model, Sec-CH-UA-Platform-Version, Sec-CH-UA-Full-Version-List, Sec-CH-UA-Platform, Sec-CH-UA, UA-Bitness, UA-Arch, UA-Full-Version, UA-Mobile, UA-Model, UA-Platform-Version, UA-Platform, UA
cross-origin-embedder-policy: require-corp
cross-origin-opener-policy: same-origin
cross-origin-resource-policy: same-origin
origin-agent-cluster: ?1
permissions-policy: accelerometer=(),autoplay=(),browsing-topics=(),camera=(),clipboard-read=(),clipboard-write=(),geolocation=(),gyroscope=(),hid=(),interest-cohort=(),magnetometer=(),microphone=(),payment=(),publickey-credentials-get=(),screen-wake-lock=(),serial=(),sync-xhr=(),usb=()
referrer-policy: same-origin
x-content-options: nosniff
x-frame-options: SAMEORIGIN
cf-mitigated: challenge
cf-chl-out: OCBTQzEQbxhCs82rWyKx7grWWwpnhl8r/A6tFqSPx9xsQ+OynhwAa+nCw7HuGd2heQcraxgHkBTM4amV0ZOVMwWN8pMsnX+BbkJiy37lJQa3v433fLQpxtLRsJHzfPEWMq6U4Gilyk8FPTEYDKIgSg==$OzKkUvVPOIiw6efUZj0n9g==
cache-control: private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0
expires: Thu, 01 Jan 1970 00:00:01 GMT
set-cookie: __cf_bm=yIB5UEaO7sffuHaa7xnoXmAJteAvJpoCmMlx27d_HDs-1727752851-1.0.1.1-SuPWwPt3CuEwNQl1dyTVaoRFtbOcuUerfReiov3YQvbF67E5LQjtvRPJiV2C1syjIqzQpNUTPcVFY9yz6dSxnA; path=/; expires=Tue, 01-Oct-24 03:50:51 GMT; domain=.li.me; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 8cb951b93ecd66f1-AMS
DNS records:
A address15.197.198.30
ttl600
A address3.33.247.24
ttl600
MX exchangeaspmx2.googlemail.com
priority40
MX exchangeaspmx3.googlemail.com
priority50
MX exchangeaspmx.l.google.com
priority10
MX exchangealt1.aspmx.l.google.com
priority20
MX exchangealt2.aspmx.l.google.com
priority30
NS valuens46.domaincontrol.com
NS valuens45.domaincontrol.com
TXT entriesstripe-verification=acce39cb4a829d156d5aa57015d97edce965ac746003e1796aead028353a0e43
TXT entriesmonday-com-verification=ttvtkdIseTweppoPaRGb5SZfZsJgd0wkfpDYEH5ZbxQ
TXT entriesDBE6D07EE4
TXT entriessending_domain1013162=cdb707938e2db5199131c2069ab0794ac03b9b58995c2dacdb50d77d048ff6be
TXT entriesgoogle-site-verification=PoUWylfoPq9kNg-nbC4TJUsfMtAdhpSb2AlpbnUfGFc
TXT entriesdocusign=3530145b-f61d-40dc-b453-ff5248698568
TXT entriesv=spf1 include:_spf.google.com include:spf.dynect.net include:mail.zendesk.com include:mailgun.org include:826d94.workshop-spf.net include:_spf.psm.knowbe4.com include:aspmx.pardot.com include:amazonses.com ~all
TXT entriesgoogle-site-verification=tecTpZ8rC77O6XDUJ0VD2H1rAMY0di8p9hAwq5Ga3KM
TXT entriesapple-domain-verification=qDAkPA73kdO5Nyta
TXT entriesatlassian-domain-verification=AY/fyfUHW5+XNgyZIUXDWvGP52ZYOkyGoq+9nAGM1NRcOfHVvTbQprTcil/iRByc
TXT entriesgoogle-site-verification=54tlf8wp0vCMLX7mxcGHbVjcBJVpBuymW3Bdd7Bw3Pg
TXT entriesgoogle-site-verification=tgcWqAXU9CS_BNRcmDIfcFKiu2Xl7ByPsGbKcVpY4bg
TXT entriesonetrust-domain-verification=c3173e6ee4174767b23c636d60e83313
TXT entriesatlassian-domain-verification=UhlB3UVjJpuBOmJ/Z0zrEGZBv8XfWTN8v2bFcgoLYgNa9gYhwYlFZzuY/G5Tnr9j
TXT entriesrm_verify=ffeb06a00b
TXT entriesv=verifydomain MS=2961774
TXT entriesgoogle-site-verification=JrpED4DnLWIYbUmf_sQ485YKsB0t8rI_AvFk8YwY19A
TXT entriesasv=0d898dc558c47a17b55368079efc075d
TXT entriesuber-domain-verification=5a0a8ccc-c980-4e8d-9d5c-86e679a2e572
TXT entriespardot1013162=2f2f97731db76a6ad8247661ffbd7d5a512cb1b5a67ab4e54fc426b6e6a4c156
TXT entriesgoogle-site-verification=dCJY1fAW_T714zz2IN4JYfRHJ8vlBJ1FalBsdikL4qA
SOA nsnamens45.domaincontrol.com
hostmasterdns.jomax.net
serial2024081201
refresh28800
retry7200
expire604800
minttl600

How to solve problems with li.me

Errors on the li.me 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 li.me on your own.