Alternatives to dealersync.com
Matched automatically on description, category and technology. Only sites that pass our safety checks are shown. · Report a wrong match
dealersync.com was registered on 20 Apr 2005 and is hosted on AS16509 Amazon.com Inc. 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.
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 dealersync.com. Refresh the analysis to check again.
1 similar domain registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| dialersync.xyz | Typo | 16 Sept 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is dealersync.com’s name taken on other extensions?
Estimated visitors and engagement.
Every IP address dealersync.com resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| dealersync.com | 52.219.113.83 | 5 |
| Host | Mail server | TTL |
|---|---|---|
| dealersync.com | 1 aspmx.l.google.com | 3600 |
| dealersync.com | 5 alt1.aspmx.l.google.com | 3600 |
| dealersync.com | 5 alt2.aspmx.l.google.com | 3600 |
| dealersync.com | 10 alt3.aspmx.l.google.com | 3600 |
| dealersync.com | 10 alt4.aspmx.l.google.com | 3600 |
| Host | Name server | TTL |
|---|---|---|
| dealersync.com | ns-1486.awsdns-57.org | 86400 |
| dealersync.com | ns-2021.awsdns-60.co.uk | 86400 |
| dealersync.com | ns-536.awsdns-03.net | 86400 |
| dealersync.com | ns-76.awsdns-09.com | 86400 |
| Host | Text | TTL |
|---|---|---|
| dealersync.com | "google-site-verification=k2g1O-zVhZB_WA-3bYtjGmo6CEcwPP0sCMI3lgEU8gc" | 3600 |
| dealersync.com | "google-site-verification=Sud3hV5-96Xs6Ez-ueDJHqLi86-bN-AW5omqJ_GaDsw" | 3600 |
| dealersync.com | "MS=3F0DFAACDAE29DA75F32B359D0050963C898421F" | 3600 |
| dealersync.com | "v=spf1 include:_netblocks.google.com include:_netblocks2.google.com include:_netblocks3.google.com include:mail.zendesk.com include:sendgrid.net include:one.zoho.com ip4:167.89.86.222 ip4:168.245.105.98 ip4:149.72.94.206 ~all" | 3600 |
| Host | Start of authority | TTL |
|---|---|---|
| dealersync.com | ns-1486.awsdns-57.org awsdns-hostmaster.amazon.com 1 7200 900 1209600 86400 | 900 |
Other domains served from 52.219.113.67. Normal for shared hosting and CDNs.
No reviews yet. Used dealersync.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.
dealersync.com has no community safety rating yet. We couldn't read an SSL certificate on it when we last analysed it. See Security →
The registration expires on 20 Apr 2027 — in 5 months. See Overview →
dealersync.com was registered on 20 Apr 2005, making it 21 years old. See Overview →
dealersync.com is served from 1 IP address, mainly on AS16509 Amazon.com Inc. in United States of America. See Hosting →
Raw registry data for dealersync.com. May be redacted by privacy services.
{"objectClassName":"domain","handle":"151765132_DOMAIN_COM-VRSN","ldhName":"DEALERSYNC.COM","links":[{"value":"https:\/\/rdap.verisign.com\/com\/v1\/domain\/DEALERSYNC.COM","rel":"self","href":"https:\/\/rdap.verisign.com\/com\/v1\/domain\/DEALERSYNC.COM","type":"application\/rdap+json"},{"value":"https:\/\/rdap.godaddy.com\/v1\/domain\/DEALERSYNC.COM","rel":"related","href":"https:\/\/rdap.godaddy.com\/v1\/domain\/DEALERSYNC.COM","type":"application\/rdap+json"}],"status":["client delete prohibited","client renew prohibited","client transfer prohibited","client update prohibited"],"entities":[{"objectClassName":"entity","handle":"146","roles":["registrar"],"publicIds":[{"type":"IANA Registrar ID","identifier":"146"}],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text","GoDaddy.com, LLC"]]],"entities":[{"objectClassName":"entity","roles":["abuse"],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text",""],["tel",{"type":"voice"},"uri","tel:480-624-2505"],["email",{},"text","abuse@godaddy.com"]]]}]}],"events":[{"eventAction":"registration","eventDate":"2005-04-20T06:09:22Z"},{"eventAction":"expiration","eventDate":"2027-04-20T06:09:22Z"},{"eventAction":"last changed","eventDate":"2022-09-15T19:40:33Z"},{"eventAction":"last update of RDAP database","eventDate":"2023-07-11T14:35:16Z"}],"secureDNS":{"delegationSigned":false},"nameservers":[{"objectClassName":"nameserver","ldhName":"NS-1486.AWSDNS-57.ORG"},{"objectClassName":"nameserver","ldhName":"NS-2021.AWSDNS-60.CO.UK"},{"objectClassName":"nameserver","ldhName":"NS-536.AWSDNS-03.NET"},{"objectClassName":"nameserver","ldhName":"NS-76.AWSDNS-09.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.dealersync.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 dealersync.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.