betcostatic.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
65
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
65
betcostatic.com was registered on 8 Apr 2017 via EuroDNS S.A. and the registry expiry is 8 Apr 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/betcostatic.com.
betcostatic.com publishes 4 nameservers. DNSSEC is not signed.
betcostatic.com has 1 IPv4 address (104.155.125.45). The geolocation database places 104.155.125.45 in Brussels, Belgium.
The TLS certificate from YR1 is valid and has 59 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Apache HTTP Server. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for betcostatic.com in the checks that ran.
betcostatic.com was registered on 8 Apr 2017 via EuroDNS S.A.. The registry returned 1 status value and 6 nameservers from https://rdap.verisign.com/com/v1/domain/betcostatic.com.
| Registered | since 8 Apr 2017 |
|---|---|
| Created | 8 April 2017 |
| Updated | 2 April 2026 |
| Expires | 8 April 2027 |
| Registrar | EuroDNS S.A. |
| Status | client transfer prohibited |
| Nameservers | ns1.alphadnszone.com, ns2.alphadnszone.com, ns3.alphadnszone.com, ns4.alphadnszone.com, ns5.alphadnszone.com, ns6.alphadnszone.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/betcostatic.com |
betcostatic.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 ns1.alphadnszone.com is published for betcostatic.com in the registration record from https://rdap.verisign.com/com/v1/domain/betcostatic.com.
Nameserver ns2.alphadnszone.com is published for betcostatic.com in the registration record from https://rdap.verisign.com/com/v1/domain/betcostatic.com.
Nameserver ns3.alphadnszone.com is published for betcostatic.com in the registration record from https://rdap.verisign.com/com/v1/domain/betcostatic.com.
Nameserver ns4.alphadnszone.com is published for betcostatic.com in the registration record from https://rdap.verisign.com/com/v1/domain/betcostatic.com.
Nameserver ns5.alphadnszone.com is published for betcostatic.com in the registration record from https://rdap.verisign.com/com/v1/domain/betcostatic.com.
Nameserver ns6.alphadnszone.com is published for betcostatic.com in the registration record from https://rdap.verisign.com/com/v1/domain/betcostatic.com.
betcostatic.com has 1 address record, 0 mail exchangers and 4 nameservers, measured at 1.1.1.1:53.
| A | 104.155.125.45 |
|---|---|
| AAAA | — |
| NS | dns1.p07.nsone.net, dns2.p07.nsone.net, dns3.p07.nsone.net, dns4.p07.nsone.net |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 104.155.125.45 answers for betcostatic.com at resolver 1.1.1.1:53.
A random label under betcostatic.com also resolved, which means wildcard DNS is on.
betcostatic.com is placed in Brussels, Belgium by the local geolocation database (db-ip).
| Address | 104.155.125.45 |
|---|---|
| Country | Belgium |
| City | Brussels |
| Source | db-ip |
The certificate for betcostatic.com is valid, with 59 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YR1 |
|---|---|
| Subject | content.betcostatic.com |
| Valid from | 1 October 2026 |
| Valid until | 30 December 2026 |
| Days left | 59 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: betcostatic.com, content.betcostatic.com.
Tech detection checked the fetched homepage and named 1 product. Source: wappalyzergo.
Apache HTTP Server is filed under Web servers.
The homepage returned HTTP 200 in 14 ms. The target title is 0 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 14 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.
Family DNS for betcostatic.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.
betcostatic.com is placed in Brussels, Belgium.
betcostatic.com expires on 8 April 2027 according to https://rdap.verisign.com/com/v1/domain/betcostatic.com.
The registry did not return a person or a company for betcostatic.com. RDAP often redacts the registrant. The registrar on file is EuroDNS S.A..
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.