myfreemp3.to
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
HTTP 429SafeSSL: 86 days left3 years old
50
myfreemp3.to was registered on 29 Sep 2023 via humbly LLC and the registry expiry is 1 Nov 2027. WHOIS data came from RDAP at https://rdap.tonicregistry.to/rdap/domain/myfreemp3.to.
myfreemp3.to publishes 2 nameservers. DNSSEC is not signed.
myfreemp3.to has 1 IPv4 address (37.48.77.82). The geolocation database places 37.48.77.82 in Amsterdam, The Netherlands.
The TLS certificate from YR2 is valid and has 86 days left (TLS 1.3).
Tech detection named Cowboy and Erlang. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for myfreemp3.to in the checks that ran.
Domain · RDAP/WHOIS
myfreemp3.to was registered on 29 Sep 2023 via humbly LLC. The registry returned 1 status value and 2 nameservers from https://rdap.tonicregistry.to/rdap/domain/myfreemp3.to.
| Registered | since 29 Sep 2023 |
|---|---|
| Created | 29 September 2023 |
| Updated | 7 October 2026 |
| Expires | 1 November 2027 |
| Registrar | humbly LLC |
| Status | active |
| Nameservers | ns1.brainydns.com, ns2.brainydns.com |
| DNSSEC | no |
| Source | https://rdap.tonicregistry.to/rdap/domain/myfreemp3.to |
Nameserver ns1.brainydns.com is published for myfreemp3.to in the registration record from https://rdap.tonicregistry.to/rdap/domain/myfreemp3.to.
Nameserver ns2.brainydns.com is published for myfreemp3.to in the registration record from https://rdap.tonicregistry.to/rdap/domain/myfreemp3.to.
DNS
myfreemp3.to has 1 address record, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 37.48.77.82 |
|---|---|
| AAAA | — |
| NS | ns1.brainydns.com, ns2.brainydns.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 37.48.77.82 answers for myfreemp3.to at resolver 1.1.1.1:53.
A random label under myfreemp3.to also resolved, which means wildcard DNS is on.
Hosting and geo
myfreemp3.to is placed in Amsterdam, The Netherlands by the local geolocation database (db-ip).
| Address | 37.48.77.82 |
|---|---|
| Country | The Netherlands |
| City | Amsterdam |
| Source | db-ip |
SSL/TLS
The certificate for myfreemp3.to is valid, with 86 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YR2 |
|---|---|
| Subject | myfreemp3.to |
| Valid from | 28 October 2026 |
| Valid until | 26 January 2027 |
| Days left | 86 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.myfreemp3.to, myfreemp3.to.
Tech stack
Tech detection checked the fetched homepage and named 2 products. Source: wappalyzergo.
- Cowboy · Web servers
- Erlang · Programming languages
Cowboy is filed under Web servers.
Erlang is filed under Programming languages.
On-page checks
The homepage returned HTTP 429 in 23 ms. The target title is 0 characters and the page has 0 H1 headings.
| Status | 429 |
|---|---|
| TTFB | 23 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 myfreemp3.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 | 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 20 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
- October 2026: dns a changed from 212.92.104.7 to 37.48.77.82.
- October 2026: dns ns changed from ns1.magpiedns.com,ns2.magpiedns.com to ns1.brainydns.com,ns2.brainydns.com.
- October 2026: geo city changed from empty to Amsterdam.
- October 2026: geo country changed from empty to The Netherlands.
Questions
Is myfreemp3.to 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 myfreemp3.to?
myfreemp3.to is placed in Amsterdam, The Netherlands.
When does myfreemp3.to expire?
myfreemp3.to expires on 1 November 2027 according to https://rdap.tonicregistry.to/rdap/domain/myfreemp3.to.
Who owns myfreemp3.to?
The registry did not return a person or a company for myfreemp3.to. RDAP often redacts the registrant. The registrar on file is humbly LLC.
Sources
- RDAP source https://rdap.tonicregistry.to/rdap/domain/myfreemp3.to at 2026-10-30T15:16:37Z
- DNS source 1.1.1.1:53 at 2026-10-30T15:16:37Z
- TLS source tls:443 at 2026-10-30T15:16:37Z
- HTTP source https://myfreemp3.to/ at 2026-10-30T15:16:37Z
- Tech source wappalyzergo at 2026-10-30T15:16:37Z
- Geo source db-ip at 2026-10-30T15:16:37Z
- Safety source family DNS and local lists at 2026-10-30T15:16:37Z
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.