jimeng3.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
55
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
55
jimeng3.com was registered on 23 Mar 2022 via NameSilo, LLC and the registry expiry is 23 Mar 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/jimeng3.com.
jimeng3.com publishes 2 nameservers. DNSSEC is not signed.
jimeng3.com has 2 IPv4 addresses (104.21.56.87, 172.67.181.180) and 2 IPv6 addresses (2606:4700:3032::6815:3857, 2606:4700:3032::ac43:b5b4). The geolocation database places 104.21.56.87 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 44 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, Cloudflare Browser Insights, Google Analytics, HSTS, HTTP/3 and jQuery. The fingerprints ran on the homepage that was already downloaded.
jimeng3.com was registered on 23 Mar 2022 via NameSilo, LLC. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/jimeng3.com.
| Registered | since 23 Mar 2022 |
|---|---|
| Created | 23 March 2022 |
| Updated | 24 March 2026 |
| Expires | 23 March 2027 |
| Registrar | NameSilo, LLC |
| Status | client transfer prohibited |
| Nameservers | owen.ns.cloudflare.com, stephane.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/jimeng3.com |
jimeng3.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 owen.ns.cloudflare.com is published for jimeng3.com in the registration record from https://rdap.verisign.com/com/v1/domain/jimeng3.com.
Nameserver stephane.ns.cloudflare.com is published for jimeng3.com in the registration record from https://rdap.verisign.com/com/v1/domain/jimeng3.com.
jimeng3.com has 4 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.56.87, 172.67.181.180 |
|---|---|
| AAAA | 2606:4700:3032::6815:3857, 2606:4700:3032::ac43:b5b4 |
| NS | owen.ns.cloudflare.com, stephane.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 104.21.56.87 answers for jimeng3.com at resolver 1.1.1.1:53.
IPv4 address 172.67.181.180 answers for jimeng3.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3032::6815:3857 answers for jimeng3.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3032::ac43:b5b4 answers for jimeng3.com at resolver 1.1.1.1:53.
jimeng3.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.56.87 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
The certificate for jimeng3.com is valid, with 44 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | jimeng3.com |
| Valid from | 15 September 2026 |
| Valid until | 14 December 2026 |
| Days left | 44 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.jimeng3.com, jimeng3.com.
Tech detection checked the fetched homepage and named 6 products. Source: wappalyzergo.
Cloudflare is filed under CDN.
Cloudflare Browser Insights is filed under Analytics, RUM.
Google Analytics is filed under Analytics.
HSTS is filed under Security.
HTTP/3 is filed under Miscellaneous.
jQuery is filed under JavaScript libraries.
The homepage returned HTTP 200 in 378 ms. The target title is 17 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 378 ms |
| Title length | 17 yes |
| Quoted title | "激萌导航 - 最激萌的福利网址导航" |
| Meta description | "激萌导航是一款最激萌的福利网址导航站点!我们及時收錄最新的宅男网站、萌妹网站、技术网站等宅男喜闻乐见的內容。讓您獲得更加簡單快捷の激萌體驗!" yes |
| H1 count | 0 |
| HSTS | yes yes |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | — |
| Links | 554 |
| Images | 44 |
| Favicon | yes |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Family DNS for jimeng3.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 | yes |
| CSP | no |
Cloudflare family DNS returned a block for jimeng3.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.
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 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.
First checked on 30 October 2026; changes will appear here.
Cloudflare family DNS returned a block for jimeng3.com. That resolver covers adult and malware names.
jimeng3.com is placed in Toronto, Canada.
jimeng3.com expires on 23 March 2027 according to https://rdap.verisign.com/com/v1/domain/jimeng3.com.
The registry did not return a person or a company for jimeng3.com. RDAP often redacts the registrant. The registrar on file is NameSilo, LLC.
No other indexable reports share this TLD, host, or registrar yet.
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.
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.