betbanks.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 52 days left19 years oldTranco #697511
75
betbanks.com was registered on 5 Jun 2007 via NameSilo, LLC and the registry expiry is 5 Jun 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/betbanks.com.
betbanks.com publishes 2 nameservers. DNSSEC is not signed.
betbanks.com has 2 IPv4 addresses (104.21.34.198, 172.67.164.120). The geolocation database places 104.21.34.198 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 52 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, HSTS, HTTP/3 and PHP. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for betbanks.com in the checks that ran.
Domain · RDAP/WHOIS
betbanks.com was registered on 5 Jun 2007 via NameSilo, LLC. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/betbanks.com.
| Registered | since 5 Jun 2007 |
|---|---|
| Created | 5 June 2007 |
| Updated | 1 September 2025 |
| Expires | 5 June 2027 |
| Registrar | NameSilo, LLC |
| Status | client transfer prohibited |
| Nameservers | asa.ns.cloudflare.com, west.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/betbanks.com |
betbanks.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 asa.ns.cloudflare.com is published for betbanks.com in the registration record from https://rdap.verisign.com/com/v1/domain/betbanks.com.
Nameserver west.ns.cloudflare.com is published for betbanks.com in the registration record from https://rdap.verisign.com/com/v1/domain/betbanks.com.
DNS
betbanks.com has 2 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.34.198, 172.67.164.120 |
|---|---|
| AAAA | — |
| NS | asa.ns.cloudflare.com, west.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 104.21.34.198 answers for betbanks.com at resolver 1.1.1.1:53.
IPv4 address 172.67.164.120 answers for betbanks.com at resolver 1.1.1.1:53.
Hosting and geo
betbanks.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.34.198 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for betbanks.com is valid, with 52 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | betbanks.com |
| Valid from | 23 September 2026 |
| Valid until | 22 December 2026 |
| Days left | 52 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.betbanks.com, betbanks.com.
Tech stack
Tech detection checked the fetched homepage and named 4 products. Source: wappalyzergo.
- Cloudflare · CDN
- HSTS · Security
- HTTP/3 · Miscellaneous
- PHP · Programming languages
Cloudflare is filed under CDN.
HSTS is filed under Security.
HTTP/3 is filed under Miscellaneous.
PHP is filed under Programming languages.
On-page checks
The homepage returned HTTP 200 in 0 ms. The target title is 0 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 0 ms |
| Title length | 0 no |
| Quoted title | none |
| Meta description | none no |
| H1 count | 0 |
| HSTS | yes yes |
| CSP | no |
| X-Frame-Options | SAMEORIGIN |
| 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 betbanks.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 | yes |
| 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 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 10 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.
Change history
First checked on 30 October 2026; changes will appear here.
Questions
Is betbanks.com 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 betbanks.com?
betbanks.com is placed in Toronto, Canada.
When does betbanks.com expire?
betbanks.com expires on 5 June 2027 according to https://rdap.verisign.com/com/v1/domain/betbanks.com.
Who owns betbanks.com?
The registry did not return a person or a company for betbanks.com. RDAP often redacts the registrant. The registrar on file is NameSilo, LLC.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/betbanks.com at 2026-10-30T13:46:49Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:46:49Z
- TLS source tls:443 at 2026-10-30T13:46:49Z
- HTTP source https://betbanks.com/ at 2026-10-30T13:46:49Z
- Tech source wappalyzergo at 2026-10-30T13:46:49Z
- Geo source db-ip at 2026-10-30T13:46:49Z
- Safety source family DNS and local lists at 2026-10-30T13:46:49Z
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.