rexupdigital.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafeSSL: -5 days left5 years old
35
rexupdigital.com was registered on 15 Apr 2021 via Cloudflare, Inc. and the registry expiry is 15 Apr 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/rexupdigital.com.
rexupdigital.com publishes 2 nameservers. DNSSEC is not signed.
rexupdigital.com has 1 IPv4 address (49.12.171.137). The geolocation database places 49.12.171.137 in Falkenstein, Germany.
The TLS certificate from YR2 is not valid (TLS 1.3).
No safety warning was recorded for rexupdigital.com in the checks that ran.
Domain · RDAP/WHOIS
rexupdigital.com was registered on 15 Apr 2021 via Cloudflare, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/rexupdigital.com.
| Registered | since 15 Apr 2021 |
|---|---|
| Created | 15 April 2021 |
| Updated | 14 April 2026 |
| Expires | 15 April 2027 |
| Registrar | Cloudflare, Inc. |
| Status | client transfer prohibited |
| Nameservers | rick.ns.cloudflare.com, tegan.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/rexupdigital.com |
rexupdigital.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 rick.ns.cloudflare.com is published for rexupdigital.com in the registration record from https://rdap.verisign.com/com/v1/domain/rexupdigital.com.
Nameserver tegan.ns.cloudflare.com is published for rexupdigital.com in the registration record from https://rdap.verisign.com/com/v1/domain/rexupdigital.com.
DNS
rexupdigital.com has 1 address record, 5 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 49.12.171.137 |
|---|---|
| AAAA | — |
| NS | rick.ns.cloudflare.com, tegan.ns.cloudflare.com |
| MX | aspmx.l.google.com (1) Google, alt1.aspmx.l.google.com (5) Google, alt2.aspmx.l.google.com (5) Google, alt3.aspmx.l.google.com (10) Google, alt4.aspmx.l.google.com (10) Google |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at rexupdigital.com is "v=spf1 +a +mx +ip4:104.131.38.116 include:_spf.google.com ~all".
IPv4 address 49.12.171.137 answers for rexupdigital.com at resolver 1.1.1.1:53.
Mail exchanger aspmx.l.google.com has preference 1. The host is recognised as Google.
Mail exchanger alt1.aspmx.l.google.com has preference 5. The host is recognised as Google.
Mail exchanger alt2.aspmx.l.google.com has preference 5. The host is recognised as Google.
Mail exchanger alt3.aspmx.l.google.com has preference 10. The host is recognised as Google.
Mail exchanger alt4.aspmx.l.google.com has preference 10. The host is recognised as Google.
Hosting and geo
rexupdigital.com is placed in Falkenstein, Germany by the local geolocation database (db-ip).
| Address | 49.12.171.137 |
|---|---|
| Country | Germany |
| City | Falkenstein |
| Source | db-ip |
SSL/TLS
The certificate for rexupdigital.com is not valid, with -5 days left and 1 subject alternative name. Source: tls:443.
| Issuer | YR2 |
|---|---|
| Subject | www.rexupdigital.com |
| Valid from | 27 July 2026 |
| Valid until | 25 October 2026 |
| Days left | -5 |
| SAN count | 1 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: www.rexupdigital.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://rexupdigital.com/": tls: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2026-10-30T14:11:59Z is after 2026-10-25T13:10:36Z
Security
Family DNS for rexupdigital.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 5 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 Falkenstein.
- October 2026: geo country changed from empty to Germany.
Questions
Is rexupdigital.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 rexupdigital.com?
rexupdigital.com is placed in Falkenstein, Germany.
When does rexupdigital.com expire?
rexupdigital.com expires on 15 April 2027 according to https://rdap.verisign.com/com/v1/domain/rexupdigital.com.
Who owns rexupdigital.com?
The registry did not return a person or a company for rexupdigital.com. RDAP often redacts the registrant. The registrar on file is Cloudflare, Inc..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/rexupdigital.com at 2026-10-30T14:11:59Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:11:59Z
- TLS source tls:443 at 2026-10-30T14:11:59Z
- HTTP source https://rexupdigital.com/ at 2026-10-30T14:11:59Z
- Tech source not available at 2026-10-30T14:11:59Z
- Geo source db-ip at 2026-10-30T14:11:59Z
- Safety source family DNS and local lists at 2026-10-30T14:11:59Z
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.