gamebookers.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
85
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
85
gamebookers.com was registered on 13 Mar 2000 via Nom-iq Ltd. dba COM LAUDE and the registry expiry is 16 May 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/gamebookers.com.
gamebookers.com publishes 6 nameservers. DNSSEC is not signed.
gamebookers.com has 2 IPv4 addresses (195.72.134.91, 195.72.135.91). The geolocation database places 195.72.134.91 in Vienna (Landstraße), Austria.
The TLS certificate from DigiCert Global G2 TLS RSA SHA256 2020 CA1 is valid and has 71 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, Cloudflare Bot Management, Envoy, Google Tag Manager, HSTS and HTTP/3. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for gamebookers.com in the checks that ran.
gamebookers.com was registered on 13 Mar 2000 via Nom-iq Ltd. dba COM LAUDE. The registry returned 6 status values and 8 nameservers from https://rdap.verisign.com/com/v1/domain/gamebookers.com.
| Registered | since 13 Mar 2000 |
|---|---|
| Created | 13 March 2000 |
| Updated | 11 May 2026 |
| Expires | 16 May 2027 |
| Registrar | Nom-iq Ltd. dba COM LAUDE |
| Status | client delete prohibited, client transfer prohibited, client update prohibited, server delete prohibited, server transfer prohibited, server update prohibited |
| Nameservers | dns1.itsfogo.com, dns2.itsfogo.com, dns3.itsfogo.com, dns4.itsfogo.com, dns5.itsfogo.com, dns6.itsfogo.com, dns7.itsfogo.com, dns8.itsfogo.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/gamebookers.com |
gamebookers.com carries the status "client delete prohibited". The registrar has asked the registry to refuse a delete. This is an EPP status on the domain object. It does not say the website is safe, and it does not name the person who registered it.
gamebookers.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.
gamebookers.com carries the status "client update prohibited". The registrar has asked the registry to refuse updates to the domain object. Contact and nameserver changes wait until the lock is lifted by the registrar of record.
gamebookers.com carries the status "server delete prohibited". The registry itself is refusing deletes. This lock is not one the registrar can clear alone.
gamebookers.com carries the status "server transfer prohibited". The registry itself is refusing transfers. The name stays at the current registrar while the status remains.
gamebookers.com carries the status "server update prohibited". The registry itself is refusing updates to the domain object.
Nameserver dns1.itsfogo.com is published for gamebookers.com in the registration record from https://rdap.verisign.com/com/v1/domain/gamebookers.com.
Nameserver dns2.itsfogo.com is published for gamebookers.com in the registration record from https://rdap.verisign.com/com/v1/domain/gamebookers.com.
Nameserver dns3.itsfogo.com is published for gamebookers.com in the registration record from https://rdap.verisign.com/com/v1/domain/gamebookers.com.
Nameserver dns4.itsfogo.com is published for gamebookers.com in the registration record from https://rdap.verisign.com/com/v1/domain/gamebookers.com.
Nameserver dns5.itsfogo.com is published for gamebookers.com in the registration record from https://rdap.verisign.com/com/v1/domain/gamebookers.com.
Nameserver dns6.itsfogo.com is published for gamebookers.com in the registration record from https://rdap.verisign.com/com/v1/domain/gamebookers.com.
Nameserver dns7.itsfogo.com is published for gamebookers.com in the registration record from https://rdap.verisign.com/com/v1/domain/gamebookers.com.
Nameserver dns8.itsfogo.com is published for gamebookers.com in the registration record from https://rdap.verisign.com/com/v1/domain/gamebookers.com.
gamebookers.com has 2 address records, 2 mail exchangers and 6 nameservers, measured at 1.1.1.1:53.
| A | 195.72.134.91, 195.72.135.91 |
|---|---|
| AAAA | — |
| NS | dns1.itsfogo.com, dns2.itsfogo.com, dns3.itsfogo.com, dns4.itsfogo.com, dns5.itsfogo.com, dns6.itsfogo.com |
| MX | mailgate01.itsfogo.com (10), mailgate02.itsfogo.com (10) |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at gamebookers.com is "v=spf1 include:_spf.itsfogo.com include:mail.zendesk.com -all".
IPv4 address 195.72.134.91 answers for gamebookers.com at resolver 1.1.1.1:53.
IPv4 address 195.72.135.91 answers for gamebookers.com at resolver 1.1.1.1:53.
Mail exchanger mailgate01.itsfogo.com has preference 10.
Mail exchanger mailgate02.itsfogo.com has preference 10.
gamebookers.com is placed in Vienna (Landstraße), Austria by the local geolocation database (db-ip).
| Address | 195.72.134.91 |
|---|---|
| Country | Austria |
| City | Vienna (Landstraße) |
| Source | db-ip |
The certificate for gamebookers.com is valid, with 71 days left and 2 subject alternative names. Source: tls:443.
| Issuer | DigiCert Global G2 TLS RSA SHA256 2020 CA1 |
|---|---|
| Subject | *.gamebookers.com |
| Valid from | 10 December 2025 |
| Valid until | 10 January 2027 |
| Days left | 71 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.gamebookers.com, gamebookers.com.
Tech detection checked the fetched homepage and named 6 products. Source: wappalyzergo.
Cloudflare is filed under CDN.
Cloudflare Bot Management is filed under Security.
Envoy is filed under Reverse proxies.
Google Tag Manager is filed under Tag managers.
HSTS is filed under Security.
HTTP/3 is filed under Miscellaneous.
The homepage returned HTTP 200 in 24 ms. The target title is 11 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 24 ms |
| Title length | 11 yes |
| Quoted title | "gamebookers" |
| Meta description | none no |
| H1 count | 0 |
| HSTS | yes yes |
| CSP | yes |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | — |
| Canonical | https://www.gamebookers.com/en/sports |
| Language | en |
| Links | 0 |
| Images | 1 |
| 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 gamebookers.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 | yes |
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 5 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 15 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.
gamebookers.com is placed in Vienna (Landstraße), Austria.
gamebookers.com expires on 16 May 2027 according to https://rdap.verisign.com/com/v1/domain/gamebookers.com.
The registry did not return a person or a company for gamebookers.com. RDAP often redacts the registrant. The registrar on file is Nom-iq Ltd. dba COM LAUDE.
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.