bidforclicks.com was registered on 17 Feb 2021 and is hosted on AS26496 in United States. 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 bidforclicks.com. Refresh the analysis to check again.
No similar domains registered in the last 90 days.
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is bidforclicks.com’s name taken on other extensions?
Every IP address bidforclicks.com resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| bidforclicks.com | 68.178.145.223 | 10791 |
| Host | Mail server | TTL |
|---|---|---|
| bidforclicks.com | 1 aspmx.l.google.com | 3600 |
| bidforclicks.com | 5 alt1.aspmx.l.google.com | 3600 |
| bidforclicks.com | 5 alt2.aspmx.l.google.com | 3600 |
| bidforclicks.com | 10 alt3.aspmx.l.google.com | 3600 |
| bidforclicks.com | 10 alt4.aspmx.l.google.com | 3600 |
| Host | Name server | TTL |
|---|---|---|
| bidforclicks.com | ns27.domaincontrol.com | 3600 |
| bidforclicks.com | ns28.domaincontrol.com | 3600 |
| Host | Text | TTL |
|---|---|---|
| bidforclicks.com | "_globalsign-domain-verification=eISiY7IwTlCNwI2Uwuq6sIc462SXO1e_HgbjHi5Rhh" | 3600 |
| bidforclicks.com | "google-site-verification=pjDJCstF9neXwpgeTntQD3RYe1WIJNNWN04Mqdtt1-4" | 3600 |
| bidforclicks.com | "v=spf1 include:dc-aa8e722993._spfm.bidforclicks.com ~all" | 3600 |
| Host | Start of authority | TTL |
|---|---|---|
| bidforclicks.com | ns27.domaincontrol.com dns.jomax.net 2023052200 28800 7200 604800 600 | 3600 |
Other domains served from 68.178.145.223. Normal for shared hosting and CDNs.
No reviews yet. Used bidforclicks.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.
bidforclicks.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 expired on 17 Feb 2024. See Overview →
bidforclicks.com was registered on 17 Feb 2021, making it 5 years old. See Overview →
bidforclicks.com is served from 1 IP address, mainly on AS26496 in United States. See Hosting →
Raw registry data for bidforclicks.com. May be redacted by privacy services.
{"objectClassName":"domain","handle":"2591968947_DOMAIN_COM-VRSN","ldhName":"BIDFORCLICKS.COM","links":[{"value":"https:\/\/rdap.verisign.com\/com\/v1\/domain\/BIDFORCLICKS.COM","rel":"self","href":"https:\/\/rdap.verisign.com\/com\/v1\/domain\/BIDFORCLICKS.COM","type":"application\/rdap+json"},{"value":"https:\/\/rdap.godaddy.com\/v1\/domain\/BIDFORCLICKS.COM","rel":"related","href":"https:\/\/rdap.godaddy.com\/v1\/domain\/BIDFORCLICKS.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":"2021-02-17T15:28:00Z"},{"eventAction":"expiration","eventDate":"2024-02-17T15:28:00Z"},{"eventAction":"last changed","eventDate":"2022-10-28T05:42:01Z"},{"eventAction":"last update of RDAP database","eventDate":"2023-07-07T02:22:22Z"}],"secureDNS":{"delegationSigned":false},"nameservers":[{"objectClassName":"nameserver","ldhName":"NS27.DOMAINCONTROL.COM"},{"objectClassName":"nameserver","ldhName":"NS28.DOMAINCONTROL.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.bidforclicks.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 bidforclicks.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.