tumbex.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafeSSL: -117 days left12 years oldTranco #7337
45
tumbex.com was registered on 20 May 2014 via OVH sas and the registry expiry is 20 May 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/tumbex.com.
tumbex.com publishes 2 nameservers. DNSSEC is signed.
tumbex.com has 1 IPv4 address (94.23.30.127). The geolocation database places 94.23.30.127 in Roubaix, France.
The TLS certificate from R12 is not valid (TLS 1.2).
No safety warning was recorded for tumbex.com in the checks that ran.
Domain · RDAP/WHOIS
tumbex.com was registered on 20 May 2014 via OVH sas. The registry returned 2 status values and 2 nameservers from https://rdap.verisign.com/com/v1/domain/tumbex.com.
| Registered | since 20 May 2014 |
|---|---|
| Created | 20 May 2014 |
| Updated | 21 May 2026 |
| Expires | 20 May 2027 |
| Registrar | OVH sas |
| Status | client delete prohibited, client transfer prohibited |
| Nameservers | dns200.anycast.me, ns200.anycast.me |
| DNSSEC | yes |
| Source | https://rdap.verisign.com/com/v1/domain/tumbex.com |
tumbex.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.
tumbex.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 dns200.anycast.me is published for tumbex.com in the registration record from https://rdap.verisign.com/com/v1/domain/tumbex.com.
Nameserver ns200.anycast.me is published for tumbex.com in the registration record from https://rdap.verisign.com/com/v1/domain/tumbex.com.
DNS
tumbex.com has 1 address record, 3 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 94.23.30.127 |
|---|---|
| AAAA | — |
| NS | dns200.anycast.me, ns200.anycast.me |
| MX | mx1.mail.ovh.net (1), mx2.mail.ovh.net (5), mx3.mail.ovh.net (100) |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at tumbex.com is "v=spf1 include:mx.ovh.com ~all".
The DMARC text record at _dmarc.tumbex.com is "v=DMARC1; p=none; sp=none; rua=mailto:[email protected]!10m; ruf=mailto:[email protected]!10m; rf=afrf; pct=100; ri=86400".
IPv4 address 94.23.30.127 answers for tumbex.com at resolver 1.1.1.1:53.
Mail exchanger mx1.mail.ovh.net has preference 1.
Mail exchanger mx2.mail.ovh.net has preference 5.
Mail exchanger mx3.mail.ovh.net has preference 100.
Hosting and geo
tumbex.com is placed in Roubaix, France by the local geolocation database (db-ip).
| Address | 94.23.30.127 |
|---|---|
| Country | France |
| City | Roubaix |
| Source | db-ip |
SSL/TLS
The certificate for tumbex.com is not valid, with -117 days left and 1 subject alternative name. Source: tls:443.
| Issuer | R12 |
|---|---|
| Subject | tumbex.com |
| Valid from | 7 April 2026 |
| Valid until | 6 July 2026 |
| Days left | -117 |
| SAN count | 1 |
| Protocol | TLS 1.2 |
| Source | tls:443 |
Subject alternative names: tumbex.com.
Validation result: certificate did not validate
Tech stack
Tech detection did not run.
| Checked | no |
|---|---|
| Source | wappalyzergo |
On-page checks
The homepage fetch did not return a status code.
| Status | none |
|---|
Get "https://tumbex.com/": tls: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2026-10-30T14:17:58Z is after 2026-07-06T05:25:34Z
Security
Family DNS for tumbex.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.
Score breakdown
Availability 10 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.
TLS 0 of 20. A valid certificate, with extra points when it has at least 14 days left.
DNS hygiene 15 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.
Change history
- October 2026: geo city changed from empty to Roubaix.
- October 2026: geo country changed from empty to France.
Questions
Is tumbex.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 tumbex.com?
tumbex.com is placed in Roubaix, France.
When does tumbex.com expire?
tumbex.com expires on 20 May 2027 according to https://rdap.verisign.com/com/v1/domain/tumbex.com.
Who owns tumbex.com?
The registry did not return a person or a company for tumbex.com. RDAP often redacts the registrant. The registrar on file is OVH sas.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/tumbex.com at 2026-10-30T14:17:58Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:17:58Z
- TLS source tls:443 at 2026-10-30T14:17:58Z
- HTTP source https://tumbex.com/ at 2026-10-30T14:17:58Z
- Tech source not available at 2026-10-30T14:17:58Z
- Geo source db-ip at 2026-10-30T14:17:58Z
- Safety source family DNS and local lists at 2026-10-30T14:17:58Z
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.