robocheck.org
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafeSSL: 48 days left7 years old
35
robocheck.org was registered on 27 Sep 2019 via NameCheap, Inc. and the registry expiry is 27 Sep 2027. WHOIS data came from RDAP at https://rdap.publicinterestregistry.org/rdap/domain/robocheck.org.
robocheck.org publishes 2 nameservers. DNSSEC is not signed.
robocheck.org has 1 IPv4 address (66.29.132.5). The geolocation database places 66.29.132.5 in Los Angeles (West Los Angeles), United States.
The TLS certificate from Sectigo Public Server Authentication CA DV R36 is not valid (TLS 1.3).
No safety warning was recorded for robocheck.org in the checks that ran.
Domain · RDAP/WHOIS
robocheck.org was registered on 27 Sep 2019 via NameCheap, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.publicinterestregistry.org/rdap/domain/robocheck.org.
| Registered | since 27 Sep 2019 |
|---|---|
| Created | 27 September 2019 |
| Updated | 2 September 2026 |
| Expires | 27 September 2027 |
| Registrar | NameCheap, Inc. |
| Status | client transfer prohibited |
| Nameservers | dns1.namecheaphosting.com, dns2.namecheaphosting.com |
| DNSSEC | no |
| Source | https://rdap.publicinterestregistry.org/rdap/domain/robocheck.org |
robocheck.org 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 dns1.namecheaphosting.com is published for robocheck.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/robocheck.org.
Nameserver dns2.namecheaphosting.com is published for robocheck.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/robocheck.org.
DNS
robocheck.org has 1 address record, 3 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 66.29.132.5 |
|---|---|
| AAAA | — |
| NS | dns1.namecheaphosting.com, dns2.namecheaphosting.com |
| MX | mx1-hosting.jellyfish.systems (10), mx2-hosting.jellyfish.systems (20), mx3-hosting.jellyfish.systems (30) |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at robocheck.org is "v=spf1 +a +mx +ip4:66.29.132.2 +ip4:66.29.132.4 include:spf.web-hosting.com +ip4:66.29.132.5 ~all".
IPv4 address 66.29.132.5 answers for robocheck.org at resolver 1.1.1.1:53.
Mail exchanger mx1-hosting.jellyfish.systems has preference 10.
Mail exchanger mx2-hosting.jellyfish.systems has preference 20.
Mail exchanger mx3-hosting.jellyfish.systems has preference 30.
Hosting and geo
robocheck.org is placed in Los Angeles (West Los Angeles), United States by the local geolocation database (db-ip).
| Address | 66.29.132.5 |
|---|---|
| Country | United States |
| City | Los Angeles (West Los Angeles) |
| Source | db-ip |
SSL/TLS
The certificate for robocheck.org is not valid, with 48 days left and 2 subject alternative names. Source: tls:443.
| Issuer | Sectigo Public Server Authentication CA DV R36 |
|---|---|
| Subject | *.web-hosting.com |
| Valid from | 3 June 2026 |
| Valid until | 18 December 2026 |
| Days left | 48 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.web-hosting.com, web-hosting.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://robocheck.org/": tls: failed to verify certificate: x509: certificate is valid for *.web-hosting.com, web-hosting.com, not robocheck.org
Security
Family DNS for robocheck.org 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 Los Angeles (West Los Angeles).
- October 2026: geo country changed from empty to United States.
Questions
Is robocheck.org 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 robocheck.org?
robocheck.org is placed in Los Angeles (West Los Angeles), United States.
When does robocheck.org expire?
robocheck.org expires on 27 September 2027 according to https://rdap.publicinterestregistry.org/rdap/domain/robocheck.org.
Who owns robocheck.org?
The registry did not return a person or a company for robocheck.org. RDAP often redacts the registrant. The registrar on file is NameCheap, Inc..
Sources
- RDAP source https://rdap.publicinterestregistry.org/rdap/domain/robocheck.org at 2026-10-30T15:03:13Z
- DNS source 1.1.1.1:53 at 2026-10-30T15:03:13Z
- TLS source tls:443 at 2026-10-30T15:03:13Z
- HTTP source https://robocheck.org/ at 2026-10-30T15:03:13Z
- Tech source not available at 2026-10-30T15:03:13Z
- Geo source db-ip at 2026-10-30T15:03:13Z
- Safety source family DNS and local lists at 2026-10-30T15:03:13Z
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.