rghost.net
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
65
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
65
rghost.net was registered on 15 Jul 2007 via Cloudflare, Inc. and the registry expiry is 15 Jul 2027. WHOIS data came from RDAP at https://rdap.verisign.com/net/v1/domain/rghost.net.
rghost.net publishes 2 nameservers. DNSSEC is signed.
rghost.net has 2 IPv4 addresses (104.21.50.229, 172.67.212.239) and 2 IPv6 addresses (2606:4700:3032::ac43:d4ef, 2606:4700:3035::6815:32e5). The geolocation database places 104.21.50.229 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 81 days left (TLS 1.3).
No safety warning was recorded for rghost.net in the checks that ran.
rghost.net was registered on 15 Jul 2007 via Cloudflare, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/net/v1/domain/rghost.net.
| Registered | since 15 Jul 2007 |
|---|---|
| Created | 15 July 2007 |
| Updated | 15 June 2026 |
| Expires | 15 July 2027 |
| Registrar | Cloudflare, Inc. |
| Status | client transfer prohibited |
| Nameservers | amber.ns.cloudflare.com, dale.ns.cloudflare.com |
| DNSSEC | yes |
| Source | https://rdap.verisign.com/net/v1/domain/rghost.net |
rghost.net 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 amber.ns.cloudflare.com is published for rghost.net in the registration record from https://rdap.verisign.com/net/v1/domain/rghost.net.
Nameserver dale.ns.cloudflare.com is published for rghost.net in the registration record from https://rdap.verisign.com/net/v1/domain/rghost.net.
rghost.net has 4 address records, 7 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.50.229, 172.67.212.239 |
|---|---|
| AAAA | 2606:4700:3032::ac43:d4ef, 2606:4700:3035::6815:32e5 |
| NS | amber.ns.cloudflare.com, dale.ns.cloudflare.com |
| MX | aspmx.l.google.com (10) Google, alt1.aspmx.l.google.com (20) Google, alt2.aspmx.l.google.com (20) Google, aspmx2.googlemail.com (30) Google, aspmx3.googlemail.com (30) Google, aspmx4.googlemail.com (30) Google, aspmx5.googlemail.com (30) Google |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | on |
| DNSSEC | signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at rghost.net is "v=spf1 include:_spf.google.com include:spf.realisticgroup.com -all".
The DMARC text record at _dmarc.rghost.net is "v=DMARC1; p=reject; adkim=s; aspf=s;".
IPv4 address 104.21.50.229 answers for rghost.net at resolver 1.1.1.1:53.
IPv4 address 172.67.212.239 answers for rghost.net at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3032::ac43:d4ef answers for rghost.net at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3035::6815:32e5 answers for rghost.net at resolver 1.1.1.1:53.
Mail exchanger aspmx.l.google.com has preference 10. The host is recognised as Google.
Mail exchanger alt1.aspmx.l.google.com has preference 20. The host is recognised as Google.
Mail exchanger alt2.aspmx.l.google.com has preference 20. The host is recognised as Google.
Mail exchanger aspmx2.googlemail.com has preference 30. The host is recognised as Google.
Mail exchanger aspmx3.googlemail.com has preference 30. The host is recognised as Google.
Mail exchanger aspmx4.googlemail.com has preference 30. The host is recognised as Google.
Mail exchanger aspmx5.googlemail.com has preference 30. The host is recognised as Google.
A random label under rghost.net also resolved, which means wildcard DNS is on.
rghost.net is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.50.229 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
The certificate for rghost.net is valid, with 81 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | rghost.net |
| Valid from | 23 October 2026 |
| Valid until | 21 January 2027 |
| Days left | 81 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.rghost.net, rghost.net.
Tech detection did not run.
| Checked | no |
|---|---|
| Source | wappalyzergo |
The homepage fetch did not return a status code.
| Status | none |
|---|
context deadline exceeded
Family DNS for rghost.net 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 10 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 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.
First checked on 30 October 2026; changes will appear here.
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
rghost.net is placed in Toronto, Canada.
rghost.net expires on 15 July 2027 according to https://rdap.verisign.com/net/v1/domain/rghost.net.
The registry did not return a person or a company for rghost.net. RDAP often redacts the registrant. The registrar on file is Cloudflare, Inc..
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.