log-lio.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200Family DNS blockedSSL: 66 days left7 years oldTranco #23582
55
log-lio.com was registered on 29 Aug 2019 via GMO Internet Group, Inc. d/b/a Onamae.com and the registry expiry is 29 Aug 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/log-lio.com.
log-lio.com publishes 2 nameservers. DNSSEC is not signed.
log-lio.com has 2 IPv4 addresses (104.21.20.16, 172.67.190.207) and 2 IPv6 addresses (2606:4700:3034::ac43:becf, 2606:4700:3036::6815:1410). The geolocation database places 104.21.20.16 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 66 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, GSAP, Google Analytics, HTTP/3, LazySizes unveilhooks plugin, LiteSpeed, LiteSpeed Cache, Litespeed Cache, MySQL, PHP, Slick, WordPress, YouTube, cdnjs, jQuery and jQuery Migrate. The fingerprints ran on the homepage that was already downloaded.
Domain · RDAP/WHOIS
log-lio.com was registered on 29 Aug 2019 via GMO Internet Group, Inc. d/b/a Onamae.com. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/log-lio.com.
| Registered | since 29 Aug 2019 |
|---|---|
| Created | 29 August 2019 |
| Updated | 29 July 2026 |
| Expires | 29 August 2027 |
| Registrar | GMO Internet Group, Inc. d/b/a Onamae.com |
| Status | client transfer prohibited |
| Nameservers | blakely.ns.cloudflare.com, mitch.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/log-lio.com |
log-lio.com 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.
Nameserver blakely.ns.cloudflare.com is published for log-lio.com in the registration record from https://rdap.verisign.com/com/v1/domain/log-lio.com.
Nameserver mitch.ns.cloudflare.com is published for log-lio.com in the registration record from https://rdap.verisign.com/com/v1/domain/log-lio.com.
DNS
log-lio.com has 4 address records, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.20.16, 172.67.190.207 |
|---|---|
| AAAA | 2606:4700:3034::ac43:becf, 2606:4700:3036::6815:1410 |
| NS | blakely.ns.cloudflare.com, mitch.ns.cloudflare.com |
| MX | _dc-mx.098528d242ae.log-lio.com (0) |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at log-lio.com is "v=spf1 +a +mx +ip4:150.95.54.200 +ip4:150.95.59.11 +ip4:150.95.55.10 ~all".
IPv4 address 104.21.20.16 answers for log-lio.com at resolver 1.1.1.1:53.
IPv4 address 172.67.190.207 answers for log-lio.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3034::ac43:becf answers for log-lio.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3036::6815:1410 answers for log-lio.com at resolver 1.1.1.1:53.
Mail exchanger _dc-mx.098528d242ae.log-lio.com has preference 0.
Hosting and geo
log-lio.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.20.16 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for log-lio.com is valid, with 66 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | log-lio.com |
| Valid from | 7 October 2026 |
| Valid until | 5 January 2027 |
| Days left | 66 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.log-lio.com, log-lio.com.
Tech stack
Tech detection checked the fetched homepage and named 16 products. Source: wappalyzergo.
- Cloudflare · CDN
- GSAP · JavaScript frameworks
- Google Analytics · Analytics
- HTTP/3 · Miscellaneous
- LazySizes unveilhooks plugin · JavaScript libraries, Performance
- LiteSpeed · Web servers
- LiteSpeed Cache · Caching, WordPress plugins
- Litespeed Cache · Caching, WordPress plugins
- MySQL · Databases
- PHP · Programming languages
- Slick · JavaScript libraries
- WordPress · CMS, Blogs
- YouTube · Video players
- cdnjs · CDN
- jQuery · JavaScript libraries
- jQuery Migrate · JavaScript libraries
Cloudflare is filed under CDN.
GSAP is filed under JavaScript frameworks.
Google Analytics is filed under Analytics.
HTTP/3 is filed under Miscellaneous.
LazySizes unveilhooks plugin is filed under JavaScript libraries, Performance.
LiteSpeed is filed under Web servers.
LiteSpeed Cache is filed under Caching, WordPress plugins.
Litespeed Cache is filed under Caching, WordPress plugins.
MySQL is filed under Databases.
PHP is filed under Programming languages.
Slick is filed under JavaScript libraries.
WordPress is filed under CMS, Blogs.
YouTube is filed under Video players.
cdnjs is filed under CDN.
jQuery is filed under JavaScript libraries.
jQuery Migrate is filed under JavaScript libraries.
On-page checks
The homepage returned HTTP 200 in 1300 ms. The target title is 11 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 1300 ms |
| Title length | 11 yes |
| Quoted title | "無料エロ漫画ぱらりずむ" |
| Meta description | "無料で読めるエロ漫画を毎日更新しております！初心者にも使いやすい無料エロ漫画サイトです！" yes |
| H1 count | 0 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | max-image-preview |
| Canonical | https://log-lio.com/ |
| Language | ja |
| Links | 371 |
| Images | 20 |
| Favicon | yes |
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 log-lio.com is blocked, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | blocked |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
Cloudflare family DNS returned a block for log-lio.com. That resolver covers adult and malware names.
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 5 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 0 of 15. HSTS, CSP, and X-Frame-Options or CSP frame-ancestors.
Safety lists 0 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
First checked on 30 October 2026; changes will appear here.
Questions
Is log-lio.com safe?
Cloudflare family DNS returned a block for log-lio.com. That resolver covers adult and malware names.
Who hosts log-lio.com?
log-lio.com is placed in Toronto, Canada.
When does log-lio.com expire?
log-lio.com expires on 29 August 2027 according to https://rdap.verisign.com/com/v1/domain/log-lio.com.
Who owns log-lio.com?
The registry did not return a person or a company for log-lio.com. RDAP often redacts the registrant. The registrar on file is GMO Internet Group, Inc. d/b/a Onamae.com.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/log-lio.com at 2026-10-30T14:02:07Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:02:07Z
- TLS source tls:443 at 2026-10-30T14:02:07Z
- HTTP source https://log-lio.com/ at 2026-10-30T14:02:07Z
- Tech source wappalyzergo at 2026-10-30T14:02:07Z
- Geo source db-ip at 2026-10-30T14:02:07Z
- Safety source family DNS and local lists at 2026-10-30T14:02:07Z
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.