onionplay.co
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafeUnder 1 year old
37
onionplay.co was registered on 2 Sep 2026 via Sav.com, LLC - 1 and the registry expiry is 2 Sep 2027. WHOIS data came from RDAP at https://rdap.registry.co/co/domain/onionplay.co.
onionplay.co publishes 2 nameservers. DNSSEC is not signed.
onionplay.co has 1 IPv4 address (162.4.84.239). The geolocation database places 162.4.84.239 in Los Angeles, United States.
No safety warning was recorded for onionplay.co in the checks that ran.
Domain · RDAP/WHOIS
onionplay.co was registered on 2 Sep 2026 via Sav.com, LLC - 1. The registry returned 2 status values and 2 nameservers from https://rdap.registry.co/co/domain/onionplay.co.
| Registered | since 2 Sep 2026 |
|---|---|
| Created | 2 September 2026 |
| Updated | 7 September 2026 |
| Expires | 2 September 2027 |
| Registrar | Sav.com, LLC - 1 |
| Status | server transfer prohibited, client transfer prohibited |
| Nameservers | ns1.ag614.parklogic.com, ns2.ag614.parklogic.com |
| DNSSEC | no |
| Source | https://rdap.registry.co/co/domain/onionplay.co |
onionplay.co carries the status "server transfer prohibited". The registry itself is refusing transfers. The name stays at the current registrar while the status remains.
onionplay.co 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 ns1.ag614.parklogic.com is published for onionplay.co in the registration record from https://rdap.registry.co/co/domain/onionplay.co.
Nameserver ns2.ag614.parklogic.com is published for onionplay.co in the registration record from https://rdap.registry.co/co/domain/onionplay.co.
DNS
onionplay.co has 1 address record, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 162.4.84.239 |
|---|---|
| AAAA | — |
| NS | ns1.ag614.parklogic.com, ns2.ag614.parklogic.com |
| MX | mx156.hostedmxserver.com (10) |
| SPF | present |
| DMARC | absent |
| CAA | issue letsencrypt.org |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at onionplay.co is "v=spf1 -all".
IPv4 address 162.4.84.239 answers for onionplay.co at resolver 1.1.1.1:53.
Mail exchanger mx156.hostedmxserver.com has preference 10.
A random label under onionplay.co also resolved, which means wildcard DNS is on.
A nameserver belongs to a parking host.
Hosting and geo
onionplay.co is placed in Los Angeles, United States by the local geolocation database (db-ip).
| Address | 162.4.84.239 |
|---|---|
| Country | United States |
| City | Los Angeles |
| Source | db-ip |
SSL/TLS
No TLS certificate was read for onionplay.co on port 443.
| Available | no |
|---|---|
| Source | tls:443 |
remote error: tls: internal error
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://onionplay.co/": tls: failed to verify certificate: x509: certificate signed by unknown authority
Security
Family DNS for onionplay.co 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 10 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 2 of 5. Five points at one year, two points at 30 days.
Change history
- October 2026: rdap created changed from empty to 2026-09-02T20:17:02.0Z.
- October 2026: rdap dnssec changed from unknown to no.
- October 2026: rdap expires changed from empty to 2027-09-02T23:59:59.0Z.
- October 2026: rdap nameservers changed from empty to ns1.ag614.parklogic.com,ns2.ag614.parklogic.com.
- October 2026: rdap registered changed from unknown to yes.
- October 2026: rdap registrar changed from empty to Sav.com, LLC - 1.
- October 2026: rdap statuses changed from empty to client transfer prohibited,server transfer prohibited.
- October 2026: rdap updated changed from empty to 2026-09-07T22:06:41.0Z.
- October 2026: tls issuer changed from YE1 to empty.
- October 2026: tls not_after changed from 2026-12-02T21:10:07Z to empty.
- October 2026: tls protocol changed from TLS 1.3 to empty.
- October 2026: geo city changed from empty to Los Angeles.
- October 2026: geo country changed from empty to United States.
Questions
Is onionplay.co 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 onionplay.co?
onionplay.co is placed in Los Angeles, United States.
When does onionplay.co expire?
onionplay.co expires on 2 September 2027 according to https://rdap.registry.co/co/domain/onionplay.co.
Who owns onionplay.co?
The registry did not return a person or a company for onionplay.co. RDAP often redacts the registrant. The registrar on file is Sav.com, LLC - 1.
Sources
- RDAP source https://rdap.registry.co/co/domain/onionplay.co at 2026-10-30T13:39:20Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:39:20Z
- TLS source tls:443 at 2026-10-30T13:39:20Z
- HTTP source https://onionplay.co/ at 2026-10-30T13:39:20Z
- Tech source not available at 2026-10-30T13:39:20Z
- Geo source db-ip at 2026-10-30T13:39:20Z
- Safety source family DNS and local lists at 2026-10-30T13:39:20Z
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.