iamfile.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 41 days left6 years old
70
iamfile.com was registered on 4 Oct 2020 via NameCheap, Inc. and the registry expiry is 4 Oct 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/iamfile.com.
iamfile.com publishes 2 nameservers. DNSSEC is not signed.
iamfile.com has 2 IPv4 addresses (13.248.169.48, 76.223.54.146). The geolocation database places 13.248.169.48 in Montreal, Canada.
The TLS certificate from GoDaddy TLS Intermediate CA DV - R1v1 is valid and has 41 days left (TLS 1.3). The homepage answered HTTP 200.
No safety warning was recorded for iamfile.com in the checks that ran.
Domain · RDAP/WHOIS
iamfile.com was registered on 4 Oct 2020 via NameCheap, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/iamfile.com.
| Registered | since 4 Oct 2020 |
|---|---|
| Created | 4 October 2020 |
| Updated | 28 October 2026 |
| Expires | 4 October 2027 |
| Registrar | NameCheap, Inc. |
| Status | client transfer prohibited |
| Nameservers | ns1.afternic.com, ns2.afternic.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/iamfile.com |
iamfile.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 ns1.afternic.com is published for iamfile.com in the registration record from https://rdap.verisign.com/com/v1/domain/iamfile.com.
Nameserver ns2.afternic.com is published for iamfile.com in the registration record from https://rdap.verisign.com/com/v1/domain/iamfile.com.
DNS
iamfile.com has 2 address records, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 13.248.169.48, 76.223.54.146 |
|---|---|
| AAAA | — |
| NS | ns1.afternic.com, ns2.afternic.com |
| MX | (0) |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at iamfile.com is "v=spf1 -all".
IPv4 address 13.248.169.48 answers for iamfile.com at resolver 1.1.1.1:53.
IPv4 address 76.223.54.146 answers for iamfile.com at resolver 1.1.1.1:53.
Mail exchanger has preference 0.
A random label under iamfile.com also resolved, which means wildcard DNS is on.
Hosting and geo
iamfile.com is placed in Montreal, Canada by the local geolocation database (db-ip).
| Address | 13.248.169.48 |
|---|---|
| Country | Canada |
| City | Montreal |
| Source | db-ip |
SSL/TLS
The certificate for iamfile.com is valid, with 41 days left and 1 subject alternative name. Source: tls:443.
| Issuer | GoDaddy TLS Intermediate CA DV - R1v1 |
|---|---|
| Subject | iamfile.com |
| Valid from | 27 May 2026 |
| Valid until | 11 December 2026 |
| Days left | 41 |
| SAN count | 1 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: iamfile.com.
Tech stack
Tech detection checked the fetched homepage and named 0 products. Source: wappalyzergo.
The fingerprint set matched no product. That is a result, not a skipped check.
On-page checks
The homepage returned HTTP 200 in 131 ms. The target title is 0 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 131 ms |
| Title length | 0 no |
| Quoted title | none |
| Meta description | none no |
| H1 count | 0 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | — |
| Links | 0 |
| Images | 0 |
| Favicon | no |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Security
Family DNS for iamfile.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 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 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 Montreal.
- October 2026: geo country changed from empty to Canada.
Questions
Is iamfile.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 iamfile.com?
iamfile.com is placed in Montreal, Canada.
When does iamfile.com expire?
iamfile.com expires on 4 October 2027 according to https://rdap.verisign.com/com/v1/domain/iamfile.com.
Who owns iamfile.com?
The registry did not return a person or a company for iamfile.com. RDAP often redacts the registrant. The registrar on file is NameCheap, Inc..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/iamfile.com at 2026-10-30T13:58:20Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:58:20Z
- TLS source tls:443 at 2026-10-30T13:58:20Z
- HTTP source https://iamfile.com/ at 2026-10-30T13:58:20Z
- Tech source wappalyzergo at 2026-10-30T13:58:20Z
- Geo source db-ip at 2026-10-30T13:58:20Z
- Safety source family DNS and local lists at 2026-10-30T13:58:20Z
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.