Alternatives to sexy.com
Matched automatically on description, category and technology. Only sites that pass our safety checks are shown. · Report a wrong match
sexy.com was registered on 20 Oct 1997 and is hosted on AS32491 Tucows.com Co. in United States of America. We couldn't read an SSL certificate for it when we last analysed it. WOT's community rates its safety very poor (10/100).
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.
We couldn't read an SSL certificate on port 443 when we last analysed sexy.com. Refresh the analysis to check again.
240 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| s3xy.world | Look-alike characters | 12 Oct 2026 | Checking… | Report → |
| s3xy.ru | Look-alike characters | 5 Oct 2026 | Checking… | Report → |
| sexy.fish | Other extension | 26 Oct 2026 | Checking… | Report → |
| sexy.rip | Other extension | 24 Oct 2026 | Checking… | Report → |
| sxey.cn | Typo | 20 Oct 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is sexy.com’s name taken on other extensions?
Every IP address sexy.com resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| sexy.com | 64.98.135.1 | 1800 |
| Host | Name server | TTL |
|---|---|---|
| sexy.com | dns1.name-services.com | 0 |
| sexy.com | dns2.name-services.com | 0 |
| sexy.com | dns3.name-services.com | 0 |
| sexy.com | dns4.name-services.com | 0 |
| sexy.com | dns5.name-services.com | 0 |
| Host | Start of authority | TTL |
|---|---|---|
| sexy.com | dns1.name-services.com info.name-services.com 1647936169 172800 900 1814400 3600 | 3600 |
Other domains served from 64.98.135.1. Normal for shared hosting and CDNs.
No reviews yet. Used sexy.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.
WOT's community rates sexy.com very poor for safety (10/100). We couldn't read an SSL certificate on it when we last analysed it. See Security →
The registration expired on 19 Oct 2023. See Overview →
sexy.com was registered on 20 Oct 1997, making it 29 years old. See Overview →
sexy.com is served from 1 IP address, mainly on AS32491 Tucows.com Co. in United States of America. See Hosting →
Raw registry data for sexy.com. May be redacted by privacy services.
{"objectClassName":"domain","handle":"2398059_DOMAIN_COM-VRSN","ldhName":"SEXY.COM","links":[{"value":"https:\/\/rdap.verisign.com\/com\/v1\/domain\/SEXY.COM","rel":"self","href":"https:\/\/rdap.verisign.com\/com\/v1\/domain\/SEXY.COM","type":"application\/rdap+json"},{"value":"https:\/\/enom.rdap.tucows.com\/domain\/SEXY.COM","rel":"related","href":"https:\/\/enom.rdap.tucows.com\/domain\/SEXY.COM","type":"application\/rdap+json"}],"status":["client transfer prohibited"],"entities":[{"objectClassName":"entity","handle":"48","roles":["registrar"],"publicIds":[{"type":"IANA Registrar ID","identifier":"48"}],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text","eNom, LLC"]]],"entities":[{"objectClassName":"entity","roles":["abuse"],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text",""],["tel",{"type":"voice"},"uri",""],["email",{},"text",""]]]}]}],"events":[{"eventAction":"registration","eventDate":"1997-10-20T04:00:00Z"},{"eventAction":"expiration","eventDate":"2023-10-19T04:00:00Z"},{"eventAction":"last changed","eventDate":"2022-09-20T06:28:37Z"},{"eventAction":"last update of RDAP database","eventDate":"2023-09-10T09:11:40Z"}],"secureDNS":{"delegationSigned":false},"nameservers":[{"objectClassName":"nameserver","ldhName":"DNS1.NAME-SERVICES.COM"},{"objectClassName":"nameserver","ldhName":"DNS2.NAME-SERVICES.COM"},{"objectClassName":"nameserver","ldhName":"DNS3.NAME-SERVICES.COM"},{"objectClassName":"nameserver","ldhName":"DNS4.NAME-SERVICES.COM"},{"objectClassName":"nameserver","ldhName":"DNS5.NAME-SERVICES.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.sexy.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 sexy.com. 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.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.
When the site first appeared, and what has changed since.
We record what changes from the next time this report is refreshed.