0p2.shop is registered with whois.nic.shop and is hosted on AS401696 in Hong Kong. Its SSL certificate doesn't cover this domain name, so browsers warn visitors.
What security vendors and the WOT community say about this domain.
What loads and tracks visitors when the homepage opens.
Running a full browser scan of the homepage… This takes about a minute.
Is 0p2.shop’s name taken on other extensions?
Every IP address 0p2.shop resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| 0p2.shop | 114.134.187.102 | 300 |
| Host | Name server | TTL |
|---|---|---|
| 0p2.shop | maleah.ns.cloudflare.com | 86400 |
| 0p2.shop | piotr.ns.cloudflare.com | 86400 |
| Host | Start of authority | TTL |
|---|---|---|
| 0p2.shop | maleah.ns.cloudflare.com dns.cloudflare.com 2413867044 10000 2400 604800 1800 | 1800 |
Other domains served from 114.134.187.102. Normal for shared hosting and CDNs.
No reviews yet. Used 0p2.shop? Be the first to say how it went.
Reviews are from CubDomain users and are separate from the security verdicts above.
Common questions, answered from this report's data.
0p2.shop has no community safety rating yet. Its SSL certificate doesn't cover this domain name, so browsers warn visitors. See Security →
0p2.shop is registered through whois.nic.shop. See WHOIS →
0p2.shop is served from 1 IP address, mainly on AS401696 in Hong Kong. See Hosting →
Raw registry data for 0p2.shop. May be redacted by privacy services.
Notice: Effective May 1, 2026, the WHOIS service has been retired in accordance with ICANN's RDAP transition policy. All registration data queries are now served via RDAP. The Registration Data Access Protocol (RDAP) base URL is: https://rdap.gmoregistry.net/rdap/
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with 0p2.shop. Data is collected independently from public sources and some figures are estimates, provided for information only.
Spam and malware blocklists for the site's IP and mail servers.
When the site first appeared, and what has changed since.
We record what changes from the next time this report is refreshed.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.