vids4me.com was registered with whois.verisign-grs.com on 6 Jan 2022 and is hosted on AS16276 OVH SAS in United States of America. 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 vids4me.com. Refresh the analysis to check again.
Is vids4me.com’s name taken on other extensions?
Every IP address vids4me.com resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| vids4me.com | 15.204.22.138 | 43193 |
| Host | Mail server | TTL |
|---|---|---|
| vids4me.com | 10 mail.vids4me.com | 43200 |
| Host | Name server | TTL |
|---|---|---|
| vids4me.com | nso133.cloudplatformpro.com | 43200 |
| vids4me.com | nso138.cloudplatformpro.com | 43200 |
| Host | Text | TTL |
|---|---|---|
| vids4me.com | "v=spf1 ip4:15.204.22.138 mx ~all" | 43200 |
| Host | Start of authority | TTL |
|---|---|---|
| vids4me.com | nso133.cloudplatformpro.com hostmaster.vids4me.com 2023061500 7200 300 1209600 10800 | 2560 |
Other domains served from 15.204.22.138. Normal for shared hosting and CDNs.
No reviews yet. Used vids4me.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.
vids4me.com has no community safety rating yet. We couldn't read an SSL certificate on it when we last analysed it. See Security →
vids4me.com is registered through whois.verisign-grs.com. See WHOIS →
The registration expired on 6 Jan 2024. See Overview →
vids4me.com was registered on 6 Jan 2022, making it 4 years old. See Overview →
vids4me.com is served from 1 IP address, mainly on AS16276 OVH SAS in United States of America. See Hosting →
Raw registry data for vids4me.com. May be redacted by privacy services.
{"objectClassName":"domain","handle":"2666318896_DOMAIN_COM-VRSN","ldhName":"VIDS4ME.COM","links":[{"value":"https:\/\/rdap.verisign.com\/com\/v1\/domain\/VIDS4ME.COM","rel":"self","href":"https:\/\/rdap.verisign.com\/com\/v1\/domain\/VIDS4ME.COM","type":"application\/rdap+json"},{"value":"https:\/\/rdapserver.net\/domain\/VIDS4ME.COM","rel":"related","href":"https:\/\/rdapserver.net\/domain\/VIDS4ME.COM","type":"application\/rdap+json"}],"status":["client transfer prohibited"],"entities":[{"objectClassName":"entity","handle":"303","roles":["registrar"],"publicIds":[{"type":"IANA Registrar ID","identifier":"303"}],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text","PDR Ltd. d\/b\/a PublicDomainRegistry.com"]]],"entities":[{"objectClassName":"entity","roles":["abuse"],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text",""],["tel",{"type":"voice"},"uri","tel:+1.2013775952"],["email",{},"text","[email protected]"]]]}]}],"events":[{"eventAction":"registration","eventDate":"2022-01-06T02:23:52Z"},{"eventAction":"expiration","eventDate":"2024-01-06T02:23:52Z"},{"eventAction":"last changed","eventDate":"2023-01-09T21:48:53Z"},{"eventAction":"last update of RDAP database","eventDate":"2023-05-26T04:02:23Z"}],"secureDNS":{"delegationSigned":false},"nameservers":[{"objectClassName":"nameserver","ldhName":"NSO133.CLOUDPLATFORMPRO.COM"},{"objectClassName":"nameserver","ldhName":"NSO138.CLOUDPLATFORMPRO.COM"}],"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.vids4me.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 vids4me.com. Data is collected independently from public sources and some figures are estimates, provided for information only.