cyberleaks.to
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafeSSL: 38 days left1 year old
40
cyberleaks.to was registered on 10 May 2025 via Tonic and the registry expiry is 1 Aug 2027. WHOIS data came from RDAP at https://rdap.tonicregistry.to/rdap/domain/cyberleaks.to.
cyberleaks.to publishes 2 nameservers. DNSSEC is not signed.
cyberleaks.to has 1 IPv4 address (162.4.84.240). The geolocation database places 162.4.84.240 in Los Angeles, United States.
The TLS certificate from YE2 is not valid (TLS 1.3).
No safety warning was recorded for cyberleaks.to in the checks that ran.
Domain · RDAP/WHOIS
cyberleaks.to was registered on 10 May 2025 via Tonic. The registry returned 1 status value and 2 nameservers from https://rdap.tonicregistry.to/rdap/domain/cyberleaks.to.
| Registered | since 10 May 2025 |
|---|---|
| Created | 10 May 2025 |
| Updated | 23 September 2026 |
| Expires | 1 August 2027 |
| Registrar | Tonic |
| Status | client transfer prohibited |
| Nameservers | ns1.kefuhw.parklogic.com, ns2.kefuhw.parklogic.com |
| DNSSEC | no |
| Source | https://rdap.tonicregistry.to/rdap/domain/cyberleaks.to |
cyberleaks.to 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.kefuhw.parklogic.com is published for cyberleaks.to in the registration record from https://rdap.tonicregistry.to/rdap/domain/cyberleaks.to.
Nameserver ns2.kefuhw.parklogic.com is published for cyberleaks.to in the registration record from https://rdap.tonicregistry.to/rdap/domain/cyberleaks.to.
DNS
cyberleaks.to has 1 address record, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 162.4.84.240 |
|---|---|
| AAAA | — |
| NS | ns1.kefuhw.parklogic.com, ns2.kefuhw.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 cyberleaks.to is "v=spf1 -all".
IPv4 address 162.4.84.240 answers for cyberleaks.to at resolver 1.1.1.1:53.
Mail exchanger mx156.hostedmxserver.com has preference 10.
A random label under cyberleaks.to also resolved, which means wildcard DNS is on.
A nameserver belongs to a parking host.
Hosting and geo
cyberleaks.to is placed in Los Angeles, United States by the local geolocation database (db-ip).
| Address | 162.4.84.240 |
|---|---|
| Country | United States |
| City | Los Angeles |
| Source | db-ip |
SSL/TLS
The certificate for cyberleaks.to is not valid, with 38 days left and 1 subject alternative name. Source: tls:443.
| Issuer | YE2 |
|---|---|
| Subject | cyberleaks.to |
| Valid from | 10 September 2026 |
| Valid until | 9 December 2026 |
| Days left | 38 |
| SAN count | 1 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: cyberleaks.to.
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://cyberleaks.to/": tls: failed to verify certificate: x509: certificate signed by unknown authority
Security
Family DNS for cyberleaks.to 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 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.
- October 2026: geo country changed from empty to United States.
Questions
Is cyberleaks.to 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 cyberleaks.to?
cyberleaks.to is placed in Los Angeles, United States.
When does cyberleaks.to expire?
cyberleaks.to expires on 1 August 2027 according to https://rdap.tonicregistry.to/rdap/domain/cyberleaks.to.
Who owns cyberleaks.to?
The registry did not return a person or a company for cyberleaks.to. RDAP often redacts the registrant. The registrar on file is Tonic.
Sources
- RDAP source https://rdap.tonicregistry.to/rdap/domain/cyberleaks.to at 2026-10-30T15:15:49Z
- DNS source 1.1.1.1:53 at 2026-10-30T15:15:49Z
- TLS source tls:443 at 2026-10-30T15:15:49Z
- HTTP source https://cyberleaks.to/ at 2026-10-30T15:15:49Z
- Tech source not available at 2026-10-30T15:15:49Z
- Geo source db-ip at 2026-10-30T15:15:49Z
- Safety source family DNS and local lists at 2026-10-30T15:15:49Z
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.