li.me
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
HTTP 403SafeSSL: 87 days left17 years oldTranco #45641
65
li.me was registered on 24 Jul 2009 via GoDaddy.com, LLC and the registry expiry is 24 Jul 2027. WHOIS data came from RDAP at https://rdap.identitydigital.services/rdap/domain/li.me.
li.me publishes 2 nameservers. DNSSEC is not signed.
li.me has 2 IPv4 addresses (15.197.198.30, 3.33.247.24). The geolocation database places 15.197.198.30 in Montreal, Canada.
The TLS certificate from Amazon RSA 2048 M01 is valid and has 87 days left (TLS 1.3).
Tech detection named Cloudflare, Cloudflare Bot Management and HTTP/3. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for li.me in the checks that ran.
Domain · RDAP/WHOIS
li.me was registered on 24 Jul 2009 via GoDaddy.com, LLC. The registry returned 4 status values and 2 nameservers from https://rdap.identitydigital.services/rdap/domain/li.me.
| Registered | since 24 Jul 2009 |
|---|---|
| Created | 24 July 2009 |
| Updated | 11 August 2026 |
| Expires | 24 July 2027 |
| Registrar | GoDaddy.com, LLC |
| Status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
| Nameservers | ns45.domaincontrol.com, ns46.domaincontrol.com |
| DNSSEC | no |
| Source | https://rdap.identitydigital.services/rdap/domain/li.me |
li.me carries the status "client delete prohibited". The registrar has asked the registry to refuse a delete. This is an EPP status on the domain object. It does not say the website is safe, and it does not name the person who registered it.
li.me carries the status "client renew prohibited". The registrar has asked the registry to refuse a renewal. The expiry date still stands until a different status is set.
li.me carries the status "client transfer prohibited". The registrar has asked the registry to refuse a transfer to another registrar. The status is a lock on the domain object. It is not evidence about the content of the site.
li.me carries the status "client update prohibited". The registrar has asked the registry to refuse updates to the domain object. Contact and nameserver changes wait until the lock is lifted by the registrar of record.
Nameserver ns45.domaincontrol.com is published for li.me in the registration record from https://rdap.identitydigital.services/rdap/domain/li.me.
Nameserver ns46.domaincontrol.com is published for li.me in the registration record from https://rdap.identitydigital.services/rdap/domain/li.me.
DNS
li.me has 2 address records, 5 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 15.197.198.30, 3.33.247.24 |
|---|---|
| AAAA | — |
| NS | ns45.domaincontrol.com, ns46.domaincontrol.com |
| MX | aspmx.l.google.com (10) Google, alt1.aspmx.l.google.com (20) Google, alt2.aspmx.l.google.com (30) Google, aspmx2.googlemail.com (40) Google, aspmx3.googlemail.com (50) Google |
| SPF | absent |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The DMARC text record at _dmarc.li.me is "v=DMARC1; p=reject; rua=mailto:[email protected]".
IPv4 address 15.197.198.30 answers for li.me at resolver 1.1.1.1:53.
IPv4 address 3.33.247.24 answers for li.me at resolver 1.1.1.1:53.
Mail exchanger aspmx.l.google.com has preference 10. The host is recognised as Google.
Mail exchanger alt1.aspmx.l.google.com has preference 20. The host is recognised as Google.
Mail exchanger alt2.aspmx.l.google.com has preference 30. The host is recognised as Google.
Mail exchanger aspmx2.googlemail.com has preference 40. The host is recognised as Google.
Mail exchanger aspmx3.googlemail.com has preference 50. The host is recognised as Google.
Hosting and geo
li.me is placed in Montreal, Canada by the local geolocation database (db-ip).
| Address | 15.197.198.30 |
|---|---|
| Country | Canada |
| City | Montreal |
| Source | db-ip |
SSL/TLS
The certificate for li.me is valid, with 87 days left and 1 subject alternative name. Source: tls:443.
| Issuer | Amazon RSA 2048 M01 |
|---|---|
| Subject | li.me |
| Valid from | 13 July 2026 |
| Valid until | 26 January 2027 |
| Days left | 87 |
| SAN count | 1 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: li.me.
Tech stack
Tech detection checked the fetched homepage and named 3 products. Source: wappalyzergo.
- Cloudflare · CDN
- Cloudflare Bot Management · Security
- HTTP/3 · Miscellaneous
Cloudflare is filed under CDN.
Cloudflare Bot Management is filed under Security.
HTTP/3 is filed under Miscellaneous.
On-page checks
The homepage returned HTTP 403 in 144 ms. The target title is 16 characters and the page has 0 H1 headings.
| Status | 403 |
|---|---|
| TTFB | 144 ms |
| Title length | 16 yes |
| Quoted title | "Just a moment..." |
| Meta description | none no |
| H1 count | 0 |
| HSTS | no no |
| CSP | yes |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | noindex,nofollow |
| Canonical | — |
| Language | en-US |
| Links | 0 |
| Images | 0 |
| Favicon | no |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Security
Family DNS for li.me is clear, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | clear |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | yes |
Google Web Risk did not run. No API key is configured, and this report does not invent a clean result from that service.
Score breakdown
Availability 10 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.
TLS 20 of 20. A valid certificate, with extra points when it has at least 14 days left.
DNS hygiene 5 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 10 of 15. HSTS, CSP, and X-Frame-Options or CSP frame-ancestors.
Safety lists 15 of 15. Points only when the checks ran and came back clean. Unknown is not clean.
Domain age 5 of 5. Five points at one year, two points at 30 days.
Change history
- October 2026: rdap created changed from 2009-07-24T13:19:54Z to 2009-07-24T13:19:54.339Z.
- October 2026: rdap dnssec changed from unknown to no.
- October 2026: rdap expires changed from 2027-07-24T13:19:54Z to 2027-07-24T13:19:54.339Z.
- October 2026: rdap statuses changed from clientdeleteprohibited,clientrenewprohibited,clienttransferprohibited,clientupdateprohibited to client delete prohibited,client renew prohibited,client transfer prohibited,client update prohibited.
- October 2026: rdap updated changed from 2026-08-11T22:56:31Z to 2026-08-11T22:56:31.032Z.
- October 2026: geo city changed from empty to Montreal.
- October 2026: geo country changed from empty to Canada.
Questions
Is li.me safe?
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
Who hosts li.me?
li.me is placed in Montreal, Canada.
When does li.me expire?
li.me expires on 24 July 2027 according to https://rdap.identitydigital.services/rdap/domain/li.me.
Who owns li.me?
The registry did not return a person or a company for li.me. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
Sources
- RDAP source https://rdap.identitydigital.services/rdap/domain/li.me at 2026-10-30T14:44:11Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:44:11Z
- TLS source tls:443 at 2026-10-30T14:44:11Z
- HTTP source https://li.me/ at 2026-10-30T14:44:11Z
- Tech source wappalyzergo at 2026-10-30T14:44:11Z
- Geo source db-ip at 2026-10-30T14:44:11Z
- Safety source family DNS and local lists at 2026-10-30T14:44:11Z
Related reports
No other indexable reports share this TLD, host, or registrar yet.
Owner of this site?
Ask for a correction or for the report to be removed from search. Public DNS facts stay on the page. An optional badge is not inserted for you.
How to read this report
The sentences under each heading are filled from the latest snapshot. If a collector had nothing to say, that sentence is left out. The target site's own title and meta description, when shown, are quoted as measurements. They are not this page's title. Change history only lists a difference between two snapshots, so the first check starts the clock and later edits are the history. A malware blocklist is the only reason the homepage body is skipped. That fact stays on the report. It does not by itself drop the page from the sitemap or from related-report links.