bingewatch.to
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
HTTP 429SafeSSL: 35 days leftUnder 1 year old
47
bingewatch.to was registered on 20 Apr 2026 via NAMECHEAP and the registry expiry is 20 Apr 2028. WHOIS data came from RDAP at https://rdap.tonicregistry.to/rdap/domain/bingewatch.to.
bingewatch.to publishes 2 nameservers. DNSSEC is not signed.
bingewatch.to has 1 IPv4 address (64.31.3.236). The geolocation database places 64.31.3.236 in Orem, United States.
The TLS certificate from YR2 is valid and has 35 days left (TLS 1.3).
Tech detection named Cowboy and Erlang. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for bingewatch.to in the checks that ran.
Domain · RDAP/WHOIS
bingewatch.to was registered on 20 Apr 2026 via NAMECHEAP. The registry returned 1 status value and 2 nameservers from https://rdap.tonicregistry.to/rdap/domain/bingewatch.to.
| Registered | since 20 Apr 2026 |
|---|---|
| Created | 20 April 2026 |
| Updated | 17 June 2026 |
| Expires | 20 April 2028 |
| Registrar | NAMECHEAP |
| Status | client transfer prohibited |
| Nameservers | ns1.brainydns.com, ns2.brainydns.com |
| DNSSEC | no |
| Source | https://rdap.tonicregistry.to/rdap/domain/bingewatch.to |
bingewatch.to 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 ns1.brainydns.com is published for bingewatch.to in the registration record from https://rdap.tonicregistry.to/rdap/domain/bingewatch.to.
Nameserver ns2.brainydns.com is published for bingewatch.to in the registration record from https://rdap.tonicregistry.to/rdap/domain/bingewatch.to.
DNS
bingewatch.to has 1 address record, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 64.31.3.236 |
|---|---|
| AAAA | — |
| NS | ns1.brainydns.com, ns2.brainydns.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 64.31.3.236 answers for bingewatch.to at resolver 1.1.1.1:53.
A random label under bingewatch.to also resolved, which means wildcard DNS is on.
Hosting and geo
bingewatch.to is placed in Orem, United States by the local geolocation database (db-ip).
| Address | 64.31.3.236 |
|---|---|
| Country | United States |
| City | Orem |
| Source | db-ip |
SSL/TLS
The certificate for bingewatch.to is valid, with 35 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YR2 |
|---|---|
| Subject | bingewatch.to |
| Valid from | 7 September 2026 |
| Valid until | 6 December 2026 |
| Days left | 35 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.bingewatch.to, bingewatch.to.
Tech stack
Tech detection checked the fetched homepage and named 2 products. Source: wappalyzergo.
- Cowboy · Web servers
- Erlang · Programming languages
Cowboy is filed under Web servers.
Erlang is filed under Programming languages.
On-page checks
The homepage returned HTTP 429 in 145 ms. The target title is 0 characters and the page has 0 H1 headings.
| Status | 429 |
|---|---|
| TTFB | 145 ms |
| Title length | 0 no |
| Quoted title | none |
| Meta description | none no |
| H1 count | 0 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | — |
| Links | 0 |
| Images | 0 |
| Favicon | no |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Security
Family DNS for bingewatch.to 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.
Score breakdown
Availability 10 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 2 of 5. Five points at one year, two points at 30 days.
Change history
- October 2026: dns a changed from 212.92.104.3 to 64.31.3.236.
- October 2026: http status_class changed from empty to 4xx.
- October 2026: tech added Cowboy.
- October 2026: tech added Erlang.
- October 2026: geo city changed from empty to Orem.
- October 2026: geo country changed from empty to United States.
Questions
Is bingewatch.to safe?
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
Who hosts bingewatch.to?
bingewatch.to is placed in Orem, United States.
When does bingewatch.to expire?
bingewatch.to expires on 20 April 2028 according to https://rdap.tonicregistry.to/rdap/domain/bingewatch.to.
Who owns bingewatch.to?
The registry did not return a person or a company for bingewatch.to. RDAP often redacts the registrant. The registrar on file is NAMECHEAP.
Sources
- RDAP source https://rdap.tonicregistry.to/rdap/domain/bingewatch.to at 2026-10-30T15:15:26Z
- DNS source 1.1.1.1:53 at 2026-10-30T15:15:26Z
- TLS source tls:443 at 2026-10-30T15:15:26Z
- HTTP source https://bingewatch.to/ at 2026-10-30T15:15:26Z
- Tech source wappalyzergo at 2026-10-30T15:15:26Z
- Geo source db-ip at 2026-10-30T15:15:26Z
- Safety source family DNS and local lists at 2026-10-30T15:15:26Z
Related reports
No other indexable reports share this TLD, host, or registrar yet.
Owner of this site?
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.
How to read this report
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.