zjmtzp.com was registered with whois.verisign-grs.com on 8 Jul 2017 and is hosted on AS45090 Shenzhen Tencent Computer Systems Company Limited in China. We couldn't read an SSL certificate for it when we last analysed it.
What security vendors and the WOT community say about this domain.
We couldn't read an SSL certificate on port 443 when we last analysed zjmtzp.com. Refresh the analysis to check again.
Is zjmtzp.com’s name taken on other extensions?
Every IP address zjmtzp.com resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| domainexpired.dnspod.cn | 119.91.230.82 | 107 |
| domainexpired.dnspod.cn | 175.178.32.60 | 107 |
| Host | Points to | TTL |
|---|---|---|
| zjmtzp.com | domainexpired-dnspod.cn | 588 |
Other domains served from 119.91.230.82. Normal for shared hosting and CDNs.
No reviews yet. Used zjmtzp.com? 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.
zjmtzp.com has no community safety rating yet. We couldn't read an SSL certificate on it when we last analysed it. See Security →
zjmtzp.com is registered through whois.verisign-grs.com. See WHOIS →
The registration expired on 8 Jul 2023. See Overview →
zjmtzp.com was registered on 8 Jul 2017, making it 9 years old. See Overview →
zjmtzp.com is served from 2 IP addresses, mainly on AS45090 Shenzhen Tencent Computer Systems Company Limited in China. See Hosting →
Raw registry data for zjmtzp.com. May be redacted by privacy services.
{"objectClassName":"domain","handle":"2141125291_DOMAIN_COM-VRSN","ldhName":"ZJMTZP.COM","links":[{"value":"https:\/\/rdap.verisign.com\/com\/v1\/domain\/ZJMTZP.COM","rel":"self","href":"https:\/\/rdap.verisign.com\/com\/v1\/domain\/ZJMTZP.COM","type":"application\/rdap+json"},{"value":"https:\/\/rdap.dnspod.cn\/domain\/ZJMTZP.COM","rel":"related","href":"https:\/\/rdap.dnspod.cn\/domain\/ZJMTZP.COM","type":"application\/rdap+json"}],"status":["client transfer prohibited"],"entities":[{"objectClassName":"entity","handle":"1697","roles":["registrar"],"publicIds":[{"type":"IANA Registrar ID","identifier":"1697"}],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text","DNSPod, Inc."]]],"entities":[{"objectClassName":"entity","roles":["abuse"],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text",""],["tel",{"type":"voice"},"uri","tel:+86.4009100100"],["email",{},"text","[email protected]"]]]}]}],"events":[{"eventAction":"registration","eventDate":"2017-07-08T15:08:52Z"},{"eventAction":"expiration","eventDate":"2023-07-08T15:08:52Z"},{"eventAction":"last changed","eventDate":"2021-12-08T03:19:36Z"},{"eventAction":"last update of RDAP database","eventDate":"2023-04-04T19:06:00Z"}],"secureDNS":{"delegationSigned":false},"nameservers":[{"objectClassName":"nameserver","ldhName":"F1G1NS1.DNSPOD.NET"},{"objectClassName":"nameserver","ldhName":"F1G1NS2.DNSPOD.NET"}],"rdapConformance":["rdap_level_0","icann_rdap_technical_implementation_guide_0","icann_rdap_response_profile_0"],"notices":[{"title":"Terms of Use","description":["Service subject to Terms of Use."],"links":[{"href":"https:\/\/www.verisign.com\/domain-names\/registration-data-access-protocol\/terms-service\/index.xhtml","type":"text\/html"}]},{"title":"Status Codes","description":["For more information on domain status codes, please visit https:\/\/icann.org\/epp"],"links":[{"href":"https:\/\/icann.org\/epp","type":"text\/html"}]},{"title":"RDDS Inaccuracy Complaint Form","description":["URL of the ICANN RDDS Inaccuracy Complaint Form: https:\/\/icann.org\/wicf"],"links":[{"href":"https:\/\/icann.org\/wicf","type":"text\/html"}]}]}The first response from http://www.zjmtzp.com, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with zjmtzp.com. Data is collected independently from public sources and some figures are estimates, provided for information only.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.