binpartner2.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
65
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
65
binpartner2.com was registered on 2 Jul 2020 via NameCheap, Inc. and the registry expiry is 2 Jul 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/binpartner2.com.
binpartner2.com publishes 2 nameservers. DNSSEC is not signed.
binpartner2.com has 2 IPv4 addresses (188.114.96.3, 188.114.97.3) and 2 IPv6 addresses (2a06:98c1:3120::3, 2a06:98c1:3121::3). The geolocation database places 188.114.96.3 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 87 days left (TLS 1.2). The homepage answered HTTP 200.
Tech detection named Cloudflare and HTTP/3. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for binpartner2.com in the checks that ran.
binpartner2.com was registered on 2 Jul 2020 via NameCheap, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/binpartner2.com.
| Registered | since 2 Jul 2020 |
|---|---|
| Created | 2 July 2020 |
| Updated | 15 June 2026 |
| Expires | 2 July 2027 |
| Registrar | NameCheap, Inc. |
| Status | client transfer prohibited |
| Nameservers | lloyd.ns.cloudflare.com, naomi.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/binpartner2.com |
binpartner2.com carries the status "client transfer prohibited". The registrar has asked the registry to refuse a transfer to another registrar. The status is a lock on the domain object. It is not evidence about the content of the site.
Nameserver lloyd.ns.cloudflare.com is published for binpartner2.com in the registration record from https://rdap.verisign.com/com/v1/domain/binpartner2.com.
Nameserver naomi.ns.cloudflare.com is published for binpartner2.com in the registration record from https://rdap.verisign.com/com/v1/domain/binpartner2.com.
binpartner2.com has 4 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 188.114.96.3, 188.114.97.3 |
|---|---|
| AAAA | 2a06:98c1:3120::3, 2a06:98c1:3121::3 |
| NS | lloyd.ns.cloudflare.com, naomi.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 188.114.96.3 answers for binpartner2.com at resolver 1.1.1.1:53.
IPv4 address 188.114.97.3 answers for binpartner2.com at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3120::3 answers for binpartner2.com at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3121::3 answers for binpartner2.com at resolver 1.1.1.1:53.
binpartner2.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 188.114.96.3 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
The certificate for binpartner2.com is valid, with 87 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | binpartner2.com |
| Valid from | 28 October 2026 |
| Valid until | 26 January 2027 |
| Days left | 87 |
| SAN count | 2 |
| Protocol | TLS 1.2 |
| Source | tls:443 |
Subject alternative names: *.binpartner2.com, binpartner2.com.
Tech detection checked the fetched homepage and named 2 products. Source: wappalyzergo.
Cloudflare is filed under CDN.
HTTP/3 is filed under Miscellaneous.
The homepage returned HTTP 200 in 71 ms. The target title is 48 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 71 ms |
| Title length | 48 yes |
| Quoted title | "Affiliate TOP - Only the best affiliate programs" |
| Meta description | "Earn up to 80% Revenue Share with lifetime payments with Affiliate Top’s top-rated affiliate program and high-converting products. Get real-time stats, daily reports, local manager support for Turnover Share, CPA & Revenue Share offers" yes |
| H1 count | 0 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | en |
| Links | 33 |
| Images | 105 |
| Favicon | yes |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Family DNS for binpartner2.com is clear, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | clear |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
Google Web Risk did not run. No API key is configured, and this report does not invent a clean result from that service.
Availability 25 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.
TLS 20 of 20. A valid certificate, with extra points when it has at least 14 days left.
DNS hygiene 0 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 0 of 15. HSTS, CSP, and X-Frame-Options or CSP frame-ancestors.
Safety lists 15 of 15. Points only when the checks ran and came back clean. Unknown is not clean.
Domain age 5 of 5. Five points at one year, two points at 30 days.
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
binpartner2.com is placed in Toronto, Canada.
binpartner2.com expires on 2 July 2027 according to https://rdap.verisign.com/com/v1/domain/binpartner2.com.
The registry did not return a person or a company for binpartner2.com. RDAP often redacts the registrant. The registrar on file is NameCheap, Inc..
No other indexable reports share this TLD, host, or registrar yet.
Ask for a correction or for the report to be removed from search. Public DNS facts stay on the page. An optional badge is not inserted for you.
The sentences under each heading are filled from the latest snapshot. If a collector had nothing to say, that sentence is left out. The target site's own title and meta description, when shown, are quoted as measurements. They are not this page's title. Change history only lists a difference between two snapshots, so the first check starts the clock and later edits are the history. A malware blocklist is the only reason the homepage body is skipped. That fact stays on the report. It does not by itself drop the page from the sitemap or from related-report links.