lybh.me
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 47 days left8 years old
70
lybh.me was registered on 4 Sep 2018 via GoDaddy.com, LLC and the registry expiry is 4 Sep 2027. WHOIS data came from RDAP at https://rdap.identitydigital.services/rdap/domain/lybh.me.
lybh.me publishes 2 nameservers. DNSSEC is not signed.
lybh.me has 2 IPv4 addresses (104.21.22.193, 172.67.206.223) and 2 IPv6 addresses (2606:4700:3035::6815:16c1, 2606:4700:3035::ac43:cedf). The geolocation database places 104.21.22.193 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 47 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, Google Analytics, HSTS, HTTP/3, MySQL, PHP, Twenty Twenty, WordPress and WordPress Block Editor. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for lybh.me in the checks that ran.
Domain · RDAP/WHOIS
lybh.me was registered on 4 Sep 2018 via GoDaddy.com, LLC. The registry returned 4 status values and 2 nameservers from https://rdap.identitydigital.services/rdap/domain/lybh.me.
| Registered | since 4 Sep 2018 |
|---|---|
| Created | 4 September 2018 |
| Updated | 19 October 2026 |
| Expires | 4 September 2027 |
| Registrar | GoDaddy.com, LLC |
| Status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
| Nameservers | max.ns.cloudflare.com, sima.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.identitydigital.services/rdap/domain/lybh.me |
lybh.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.
lybh.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.
lybh.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.
lybh.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 max.ns.cloudflare.com is published for lybh.me in the registration record from https://rdap.identitydigital.services/rdap/domain/lybh.me.
Nameserver sima.ns.cloudflare.com is published for lybh.me in the registration record from https://rdap.identitydigital.services/rdap/domain/lybh.me.
DNS
lybh.me has 4 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.22.193, 172.67.206.223 |
|---|---|
| AAAA | 2606:4700:3035::6815:16c1, 2606:4700:3035::ac43:cedf |
| NS | max.ns.cloudflare.com, sima.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 104.21.22.193 answers for lybh.me at resolver 1.1.1.1:53.
IPv4 address 172.67.206.223 answers for lybh.me at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3035::6815:16c1 answers for lybh.me at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3035::ac43:cedf answers for lybh.me at resolver 1.1.1.1:53.
Hosting and geo
lybh.me is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.22.193 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for lybh.me is valid, with 47 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | lybh.me |
| Valid from | 18 September 2026 |
| Valid until | 17 December 2026 |
| Days left | 47 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.lybh.me, lybh.me.
Tech stack
Tech detection checked the fetched homepage and named 9 products. Source: wappalyzergo.
- Cloudflare · CDN
- Google Analytics · Analytics
- HSTS · Security
- HTTP/3 · Miscellaneous
- MySQL · Databases
- PHP · Programming languages
- Twenty Twenty · WordPress themes
- WordPress · CMS, Blogs
- WordPress Block Editor · Page builders
Cloudflare is filed under CDN.
Google Analytics is filed under Analytics.
HSTS is filed under Security.
HTTP/3 is filed under Miscellaneous.
MySQL is filed under Databases.
PHP is filed under Programming languages.
Twenty Twenty is filed under WordPress themes.
WordPress is filed under CMS, Blogs.
WordPress Block Editor is filed under Page builders.
On-page checks
The homepage returned HTTP 200 in 1368 ms. The target title is 7 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 1368 ms |
| Title length | 7 yes |
| Quoted title | "冷月白狐的废墟" |
| Meta description | none no |
| H1 count | 1 |
| HSTS | yes yes |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | max-image-preview:large |
| Canonical | — |
| Language | zh-Hans |
| Links | 9 |
| 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 lybh.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 | yes |
| CSP | no |
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 25 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 0 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 5 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 2018-09-04T03:42:16Z to 2018-09-04T03:42:16.044Z.
- October 2026: rdap dnssec changed from unknown to no.
- October 2026: rdap expires changed from 2027-09-04T03:42:16Z to 2027-09-04T03:42:16.044Z.
- 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-10-19T03:43:08Z to 2026-10-19T03:43:08.831Z.
- October 2026: http hsts changed from false to true.
- October 2026: http status_class changed from empty to 2xx.
- October 2026: tech added Cloudflare.
- October 2026: tech added Google Analytics.
- October 2026: tech added HSTS.
- October 2026: tech added HTTP/3.
- October 2026: tech added MySQL.
- October 2026: tech added PHP.
- October 2026: tech added Twenty Twenty.
- October 2026: tech added WordPress.
- October 2026: tech added WordPress Block Editor.
Questions
Is lybh.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 lybh.me?
lybh.me is placed in Toronto, Canada.
When does lybh.me expire?
lybh.me expires on 4 September 2027 according to https://rdap.identitydigital.services/rdap/domain/lybh.me.
Who owns lybh.me?
The registry did not return a person or a company for lybh.me. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
Sources
- RDAP source https://rdap.identitydigital.services/rdap/domain/lybh.me at 2026-10-30T14:44:17Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:44:17Z
- TLS source tls:443 at 2026-10-30T14:44:17Z
- HTTP source https://lybh.me/ at 2026-10-30T14:44:17Z
- Tech source wappalyzergo at 2026-10-30T14:44:17Z
- Geo source db-ip at 2026-10-30T14:44:17Z
- Safety source family DNS and local lists at 2026-10-30T14:44:17Z
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.