anonfiles.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafe15 years oldTranco #137999
30
anonfiles.com was registered on 23 Mar 2011 via Tucows Domains Inc. and the registry expiry is 23 Mar 2030. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/anonfiles.com.
anonfiles.com publishes 3 nameservers. DNSSEC is not signed.
No safety warning was recorded for anonfiles.com in the checks that ran.
Domain · RDAP/WHOIS
anonfiles.com was registered on 23 Mar 2011 via Tucows Domains Inc.. The registry returned 2 status values and 3 nameservers from https://rdap.verisign.com/com/v1/domain/anonfiles.com.
| Registered | since 23 Mar 2011 |
|---|---|
| Created | 23 March 2011 |
| Updated | 4 July 2025 |
| Expires | 23 March 2030 |
| Registrar | Tucows Domains Inc. |
| Status | client transfer prohibited, client update prohibited |
| Nameservers | 1-you.njalla.no, 2-can.njalla.in, 3-get.njalla.fo |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/anonfiles.com |
anonfiles.com 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.
anonfiles.com carries the status "client update prohibited". The registrar has asked the registry to refuse updates to the domain object. Contact and nameserver changes wait until the lock is lifted by the registrar of record.
Nameserver 1-you.njalla.no is published for anonfiles.com in the registration record from https://rdap.verisign.com/com/v1/domain/anonfiles.com.
Nameserver 2-can.njalla.in is published for anonfiles.com in the registration record from https://rdap.verisign.com/com/v1/domain/anonfiles.com.
Nameserver 3-get.njalla.fo is published for anonfiles.com in the registration record from https://rdap.verisign.com/com/v1/domain/anonfiles.com.
DNS
anonfiles.com has 0 address records, 1 mail exchanger and 3 nameservers, measured at 1.1.1.1:53.
| A | — |
|---|---|
| AAAA | — |
| NS | 1-you.njalla.no, 2-can.njalla.in, 3-get.njalla.fo |
| MX | mail.anonfiles.com (10) |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
Mail exchanger mail.anonfiles.com has preference 10.
Hosting and geo
Geolocation for anonfiles.com is not available. No local city or ASN database is installed, so this report does not guess a country.
| Geolocation | not available |
|---|---|
| Source | maxmind |
SSL/TLS
No TLS certificate was read for anonfiles.com on port 443.
| Available | no |
|---|---|
| Source | tls:443 |
dial tcp: lookup anonfiles.com on 46.38.252.230:53: no such host
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://anonfiles.com/": dial tcp: lookup anonfiles.com on 46.38.252.230:53: no such host
Security
Family DNS for anonfiles.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 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 0 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 anonfiles.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 anonfiles.com?
The host network is not available without a local geolocation database.
When does anonfiles.com expire?
anonfiles.com expires on 23 March 2030 according to https://rdap.verisign.com/com/v1/domain/anonfiles.com.
Who owns anonfiles.com?
The registry did not return a person or a company for anonfiles.com. RDAP often redacts the registrant. The registrar on file is Tucows Domains Inc..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/anonfiles.com at 2026-10-30T13:44:35Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:44:35Z
- TLS source tls:443 at 2026-10-30T13:44:35Z
- HTTP source https://anonfiles.com/ at 2026-10-30T13:44:35Z
- Tech source not available at 2026-10-30T13:44:35Z
- Geo source db-ip at 2026-10-30T13:44:35Z
- Safety source family DNS and local lists at 2026-10-30T13:44:35Z
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.