Filesend.to valuation and analysis
Robots.txt Information
| Robot | Path | Permission |
| GoogleBot | / | ✔ |
| BingBot | / | ✔ |
| BaiduSpider | / | ✔ |
| YandexBot | / | ✔ |
Meta Tags
| Title | ERROR: The request could not be satisfied |
| Description | N/A |
| Keywords | N/A |
Server Information
| WebSite | |
| Host IP | 99.86.58.39 |
| Location | Seattle, Washington, United States |
Related Websites
| Site | Rank |
| datadeliver.net | #19,135 |
| gigafile.nu | #3,130 |
| file-post.net | #57,824 |
| firestorage.jp | #3,457 |
| bitpark.co.jp | #307,517 |
More to Explore
Filesend.to Valuation
|
US$234,832
Last updated: Mar 17, 2020
Filesend.to has global traffic rank of 89,337 and ranks the 22,020th in United States. Its global rank has gone up by 44,279 positions since 3 months ago. Filesend.to has an estimated worth of US$ 234,832, based on its estimated Ads revenue. Filesend.to receives approximately 35,743 unique visitors each day. Its web server is located in Seattle, Washington, United States, with IP address 99.86.58.39. According to SiteAdvisor, filesend.to is safe to visit. |
Traffic & Worth Estimates
| Purchase/Sale Value | US$234,832 |
| Daily Ads Revenue | US$128 |
| Monthly Ads Revenue | US$3,860 |
| Yearly Ads Revenue | US$46,966 |
| Daily Unique Visitors | 35,743 |
| Note: All traffic and earnings values are estimates. | |
Traffic Ranks
| Global Rank | 89,337 |
| Delta (90 Days) | ⬆️ 44,279 |
| Most Popular In Country | United States |
| Country Rank | 22,020 |
DNS Records
| Host | Type | TTL | Data |
| filesend.to | A | 59 | IP: 13.33.255.24 |
| filesend.to | A | 59 | IP: 13.33.255.81 |
| filesend.to | A | 59 | IP: 13.33.255.126 |
| filesend.to | A | 59 | IP: 13.33.255.31 |
| filesend.to | MX | 299 | Priority: 10 Target: mail.free.filesend.to. |
| filesend.to | NS | 21599 | Target: ns-1916.awsdns-47.co.uk. |
| filesend.to | NS | 21599 | Target: ns-314.awsdns-39.com. |
| filesend.to | NS | 21599 | Target: ns-949.awsdns-54.net. |
| filesend.to | NS | 21599 | Target: ns-1238.awsdns-26.org. |
| filesend.to | TXT | 59 | TXT: v=spf1 +ip4:54.92.10.105 +ip4:54.92.16.11 +ip4:54.92.31.182 +ip4:54.92.52.243 +ip4:54.92.52.247 +ip4:54.92.53.169 +ip4:54.92.53.217 +ip4:54.92.53.218 +ip4:54.92.53.223 +ip4:54.92.53.225 +ip4:52.192.22.247 +ip4:13.112.37.198" " ip4:52.193.49.217 ip4:54.65.165.183 ip4:52.198.58.239 ip4:13.112.102.98 ip4:52.196.62.96 ip4:52.199.46.176 ip4:13.112.36.172 ip4:52.192.239.64 ip4:13.113.54.245 ip4:52.198.227.188 ip4:158.201.127.1 ~all |
| filesend.to | SOA | 899 | MNAME: ns-1238.awsdns-26.org. RNAME: awsdns-hostmaster.amazon.com. Serial: 1 Refresh: 7200 Retry: 900 Expire: 1209600 Minimum TTL: 86400 |
HTTP Headers
HTTP/1.1 403 Forbidden Server: CloudFront Date: Sun, 27 Oct 2019 14:59:19 GMT Content-Type: text/html Content-Length: 915 Connection: keep-alive X-Cache: Error from cloudfront Via: 1.1 290e11478c5b9149e389233998147082.cloudfront.net (CloudFront) X-Amz-Cf-Pop: YTO50-C1 X-Amz-Cf-Id: STtSSXf6UEKYcjLWZRBc8Qbm5Y2K3CXOzWe4ts0AltrUzcZ3E9q1cA== |
Filesend.to Whois Information
Tonic whoisd V1.1 filesend ns-1238.awsdns-26.org filesend ns-314.awsdns-39.com |