rehold.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 37 days left11 years oldTranco #103637
70
rehold.com was registered on 30 Dec 2014 via NameCheap, Inc. and the registry expiry is 30 Dec 2026. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/rehold.com.
rehold.com publishes 2 nameservers. DNSSEC is not signed.
rehold.com has 2 IPv4 addresses (104.21.61.126, 172.67.210.132) and 2 IPv6 addresses (2606:4700:3031::ac43:d284, 2606:4700:3037::6815:3d7e). The geolocation database places 104.21.61.126 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 37 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare and HTTP/3. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for rehold.com in the checks that ran.
Domain · RDAP/WHOIS
rehold.com was registered on 30 Dec 2014 via NameCheap, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/rehold.com.
| Registered | since 30 Dec 2014 |
|---|---|
| Created | 30 December 2014 |
| Updated | 10 September 2026 |
| Expires | 30 December 2026 |
| Registrar | NameCheap, Inc. |
| Status | active |
| Nameservers | carlos.ns.cloudflare.com, sara.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/rehold.com |
Nameserver carlos.ns.cloudflare.com is published for rehold.com in the registration record from https://rdap.verisign.com/com/v1/domain/rehold.com.
Nameserver sara.ns.cloudflare.com is published for rehold.com in the registration record from https://rdap.verisign.com/com/v1/domain/rehold.com.
DNS
rehold.com has 4 address records, 3 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.61.126, 172.67.210.132 |
|---|---|
| AAAA | 2606:4700:3031::ac43:d284, 2606:4700:3037::6815:3d7e |
| NS | carlos.ns.cloudflare.com, sara.ns.cloudflare.com |
| MX | route3.mx.cloudflare.net (28), route1.mx.cloudflare.net (38), route2.mx.cloudflare.net (56) |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at rehold.com is "v=spf1 include:_spf.mx.cloudflare.net ~all".
IPv4 address 104.21.61.126 answers for rehold.com at resolver 1.1.1.1:53.
IPv4 address 172.67.210.132 answers for rehold.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3031::ac43:d284 answers for rehold.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3037::6815:3d7e answers for rehold.com at resolver 1.1.1.1:53.
Mail exchanger route3.mx.cloudflare.net has preference 28.
Mail exchanger route1.mx.cloudflare.net has preference 38.
Mail exchanger route2.mx.cloudflare.net has preference 56.
A random label under rehold.com also resolved, which means wildcard DNS is on.
Hosting and geo
rehold.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.61.126 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for rehold.com is valid, with 37 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | rehold.com |
| Valid from | 10 September 2026 |
| Valid until | 9 December 2026 |
| Days left | 37 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.rehold.com, rehold.com.
Tech stack
Tech detection checked the fetched homepage and named 2 products. Source: wappalyzergo.
- Cloudflare · CDN
- HTTP/3 · Miscellaneous
Cloudflare is filed under CDN.
HTTP/3 is filed under Miscellaneous.
On-page checks
The homepage returned HTTP 200 in 40 ms. The target title is 60 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 40 ms |
| Title length | 60 yes |
| Quoted title | "This Domain Has Been Transferred by Court Order — Rehold.com" |
| Meta description | none no |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | en |
| Links | 12 |
| 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 rehold.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 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 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
First checked on 30 October 2026; changes will appear here.
Questions
Is rehold.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 rehold.com?
rehold.com is placed in Toronto, Canada.
When does rehold.com expire?
rehold.com expires on 30 December 2026 according to https://rdap.verisign.com/com/v1/domain/rehold.com.
Who owns rehold.com?
The registry did not return a person or a company for rehold.com. RDAP often redacts the registrant. The registrar on file is NameCheap, Inc..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/rehold.com at 2026-10-30T14:11:40Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:11:40Z
- TLS source tls:443 at 2026-10-30T14:11:40Z
- HTTP source https://rehold.com/ at 2026-10-30T14:11:40Z
- Tech source wappalyzergo at 2026-10-30T14:11:40Z
- Geo source db-ip at 2026-10-30T14:11:40Z
- Safety source family DNS and local lists at 2026-10-30T14:11:40Z
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.