uploadrar.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
75
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
75
uploadrar.com was registered on 6 May 2018 via Name.com, Inc. and the registry expiry is 6 May 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/uploadrar.com.
uploadrar.com publishes 2 nameservers. DNSSEC is not signed.
uploadrar.com has 2 IPv4 addresses (104.21.4.98, 172.67.153.249) and 2 IPv6 addresses (2606:4700:3035::6815:462, 2606:4700:3035::ac43:99f9). The geolocation database places 104.21.4.98 in Toronto, Canada.
The TLS certificate from YE2 is valid and has 68 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Bootstrap, Cloudflare, HTTP/3, jQuery and jQuery CDN. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for uploadrar.com in the checks that ran.
uploadrar.com was registered on 6 May 2018 via Name.com, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/uploadrar.com.
| Registered | since 6 May 2018 |
|---|---|
| Created | 6 May 2018 |
| Updated | 6 May 2026 |
| Expires | 6 May 2027 |
| Registrar | Name.com, Inc. |
| Status | client transfer prohibited |
| Nameservers | davina.ns.cloudflare.com, gabriel.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/uploadrar.com |
uploadrar.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.
Nameserver davina.ns.cloudflare.com is published for uploadrar.com in the registration record from https://rdap.verisign.com/com/v1/domain/uploadrar.com.
Nameserver gabriel.ns.cloudflare.com is published for uploadrar.com in the registration record from https://rdap.verisign.com/com/v1/domain/uploadrar.com.
uploadrar.com has 4 address records, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.4.98, 172.67.153.249 |
|---|---|
| AAAA | 2606:4700:3035::6815:462, 2606:4700:3035::ac43:99f9 |
| NS | davina.ns.cloudflare.com, gabriel.ns.cloudflare.com |
| MX | _dc-mx.8e13b7165c45.uploadrar.com (10) |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at uploadrar.com is "v=spf1 +a +mx +ip4:138.201.126.22 +ip4:138.201.52.251 ~all".
IPv4 address 104.21.4.98 answers for uploadrar.com at resolver 1.1.1.1:53.
IPv4 address 172.67.153.249 answers for uploadrar.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3035::6815:462 answers for uploadrar.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3035::ac43:99f9 answers for uploadrar.com at resolver 1.1.1.1:53.
Mail exchanger _dc-mx.8e13b7165c45.uploadrar.com has preference 10.
uploadrar.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.4.98 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
The certificate for uploadrar.com is valid, with 68 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YE2 |
|---|---|
| Subject | uploadrar.com |
| Valid from | 9 October 2026 |
| Valid until | 7 January 2027 |
| Days left | 68 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.uploadrar.com, uploadrar.com.
Tech detection checked the fetched homepage and named 5 products. Source: wappalyzergo.
Bootstrap is filed under UI frameworks.
Cloudflare is filed under CDN.
HTTP/3 is filed under Miscellaneous.
jQuery is filed under JavaScript libraries.
jQuery CDN is filed under CDN.
The homepage returned HTTP 200 in 146 ms. The target title is 40 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 146 ms |
| Title length | 40 yes |
| Quoted title | "Uploadrar - Easy way to share your files" |
| Meta description | "Uploadrar - Free file upload service" yes |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | — |
| Canonical | — |
| Language | — |
| Links | 47 |
| Images | 27 |
| 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 uploadrar.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.
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 5 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.
uploadrar.com is placed in Toronto, Canada.
uploadrar.com expires on 6 May 2027 according to https://rdap.verisign.com/com/v1/domain/uploadrar.com.
The registry did not return a person or a company for uploadrar.com. RDAP often redacts the registrant. The registrar on file is Name.com, Inc..
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.