filedot.to
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
80
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
80
filedot.to was registered on 31 Jul 2022 via Tonic and the registry expiry is 31 Jul 2027. WHOIS data came from RDAP at https://rdap.tonicregistry.to/rdap/domain/filedot.to.
filedot.to publishes 2 nameservers. DNSSEC is not signed.
filedot.to has 2 IPv4 addresses (104.21.37.7, 172.67.202.41) and 2 IPv6 addresses (2606:4700:3035::6815:2507, 2606:4700:3036::ac43:ca29). The geolocation database places 104.21.37.7 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 74 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Bootstrap, BootstrapCDN, Cloudflare, Cloudflare Browser Insights, HSTS, HTTP/3 and jQuery. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for filedot.to in the checks that ran.
filedot.to was registered on 31 Jul 2022 via Tonic. The registry returned 1 status value and 2 nameservers from https://rdap.tonicregistry.to/rdap/domain/filedot.to.
| Registered | since 31 Jul 2022 |
|---|---|
| Created | 31 July 2022 |
| Updated | 17 July 2026 |
| Expires | 31 July 2027 |
| Registrar | Tonic |
| Status | active |
| Nameservers | dion.ns.cloudflare.com, jamie.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.tonicregistry.to/rdap/domain/filedot.to |
Nameserver dion.ns.cloudflare.com is published for filedot.to in the registration record from https://rdap.tonicregistry.to/rdap/domain/filedot.to.
Nameserver jamie.ns.cloudflare.com is published for filedot.to in the registration record from https://rdap.tonicregistry.to/rdap/domain/filedot.to.
filedot.to has 4 address records, 3 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.37.7, 172.67.202.41 |
|---|---|
| AAAA | 2606:4700:3035::6815:2507, 2606:4700:3036::ac43:ca29 |
| NS | dion.ns.cloudflare.com, jamie.ns.cloudflare.com |
| MX | mx.zoho.eu (10), mx2.zoho.eu (20), mx3.zoho.eu (50) |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at filedot.to is "v=spf1 include:zoho.eu ~all".
IPv4 address 104.21.37.7 answers for filedot.to at resolver 1.1.1.1:53.
IPv4 address 172.67.202.41 answers for filedot.to at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3035::6815:2507 answers for filedot.to at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3036::ac43:ca29 answers for filedot.to at resolver 1.1.1.1:53.
Mail exchanger mx.zoho.eu has preference 10.
Mail exchanger mx2.zoho.eu has preference 20.
Mail exchanger mx3.zoho.eu has preference 50.
filedot.to is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.37.7 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
The certificate for filedot.to is valid, with 74 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | filedot.to |
| Valid from | 15 October 2026 |
| Valid until | 13 January 2027 |
| Days left | 74 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.filedot.to, filedot.to.
Tech detection checked the fetched homepage and named 7 products. Source: wappalyzergo.
Bootstrap is filed under UI frameworks.
BootstrapCDN is filed under CDN.
Cloudflare is filed under CDN.
Cloudflare Browser Insights is filed under Analytics, RUM.
HSTS is filed under Security.
HTTP/3 is filed under Miscellaneous.
jQuery is filed under JavaScript libraries.
The homepage returned HTTP 200 in 156 ms. The target title is 41 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 156 ms |
| Title length | 41 yes |
| Quoted title | "filedot.to - Easy way to share your files" |
| Meta description | "filedot.to - Free file upload service" yes |
| H1 count | 0 |
| HSTS | yes yes |
| CSP | no |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | — |
| Canonical | — |
| Language | — |
| Links | 37 |
| Images | 4 |
| Favicon | yes |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Family DNS for filedot.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 | yes |
| 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 25 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 5 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 10 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.
filedot.to is placed in Toronto, Canada.
filedot.to expires on 31 July 2027 according to https://rdap.tonicregistry.to/rdap/domain/filedot.to.
The registry did not return a person or a company for filedot.to. RDAP often redacts the registrant. The registrar on file is Tonic.
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.