myf2m.net
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200Family DNS blockedSSL: 54 days left2 years old
50
myf2m.net was registered on 29 Mar 2024 via TuringSign Inc. d/b/a Cosmotown and the registry expiry is 29 Mar 2027. WHOIS data came from RDAP at https://rdap.verisign.com/net/v1/domain/myf2m.net.
myf2m.net publishes 2 nameservers. DNSSEC is not signed.
myf2m.net has 2 IPv4 addresses (188.114.96.3, 188.114.97.3) and 2 IPv6 addresses (2a06:98c1:3120::3, 2a06:98c1:3121::3). The geolocation database places 188.114.96.3 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 54 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Bootstrap, LiteSpeed, LiteSpeed Cache, Litespeed Cache, MySQL, Nginx, OpenResty, PHP, WordPress and jQuery. The fingerprints ran on the homepage that was already downloaded.
Domain · RDAP/WHOIS
myf2m.net was registered on 29 Mar 2024 via TuringSign Inc. d/b/a Cosmotown. The registry returned 4 status values and 2 nameservers from https://rdap.verisign.com/net/v1/domain/myf2m.net.
| Registered | since 29 Mar 2024 |
|---|---|
| Created | 29 March 2024 |
| Updated | 29 March 2026 |
| Expires | 29 March 2027 |
| Registrar | TuringSign Inc. d/b/a Cosmotown |
| Status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
| Nameservers | burt.ns.cloudflare.com, wren.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/net/v1/domain/myf2m.net |
myf2m.net carries the status "client delete prohibited". The registrar has asked the registry to refuse a delete. This is an EPP status on the domain object. It does not say the website is safe, and it does not name the person who registered it.
myf2m.net carries the status "client renew prohibited". The registrar has asked the registry to refuse a renewal. The expiry date still stands until a different status is set.
myf2m.net 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.
myf2m.net carries the status "client update prohibited". The registrar has asked the registry to refuse updates to the domain object. Contact and nameserver changes wait until the lock is lifted by the registrar of record.
Nameserver burt.ns.cloudflare.com is published for myf2m.net in the registration record from https://rdap.verisign.com/net/v1/domain/myf2m.net.
Nameserver wren.ns.cloudflare.com is published for myf2m.net in the registration record from https://rdap.verisign.com/net/v1/domain/myf2m.net.
DNS
myf2m.net has 4 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 188.114.96.3, 188.114.97.3 |
|---|---|
| AAAA | 2a06:98c1:3120::3, 2a06:98c1:3121::3 |
| NS | burt.ns.cloudflare.com, wren.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 188.114.96.3 answers for myf2m.net at resolver 1.1.1.1:53.
IPv4 address 188.114.97.3 answers for myf2m.net at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3120::3 answers for myf2m.net at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3121::3 answers for myf2m.net at resolver 1.1.1.1:53.
Hosting and geo
myf2m.net is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 188.114.96.3 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for myf2m.net is valid, with 54 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | myf2m.net |
| Valid from | 25 September 2026 |
| Valid until | 24 December 2026 |
| Days left | 54 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.myf2m.net, myf2m.net.
Tech stack
Tech detection checked the fetched homepage and named 10 products. Source: wappalyzergo.
- Bootstrap · UI frameworks
- LiteSpeed · Web servers
- LiteSpeed Cache · Caching, WordPress plugins
- Litespeed Cache · Caching, WordPress plugins
- MySQL · Databases
- Nginx · Web servers, Reverse proxies
- OpenResty · Web servers
- PHP · Programming languages
- WordPress · CMS, Blogs
- jQuery · JavaScript libraries
Bootstrap is filed under UI frameworks.
LiteSpeed is filed under Web servers.
LiteSpeed Cache is filed under Caching, WordPress plugins.
Litespeed Cache is filed under Caching, WordPress plugins.
MySQL is filed under Databases.
Nginx is filed under Web servers, Reverse proxies.
OpenResty is filed under Web servers.
PHP is filed under Programming languages.
WordPress is filed under CMS, Blogs.
jQuery is filed under JavaScript libraries.
On-page checks
The homepage returned HTTP 200 in 71 ms. The target title is 93 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 71 ms |
| Title length | 93 no |
| Quoted title | "فیلم 2 مدیا Film2Media فیلم تو مدیا | دانلود فیلم و سریال بدون سانسور با زیرنویس فارسی چسبیده" |
| Meta description | "دانلود فیلم بدون سانسور , دانلود رایگان فیلم , دانلود فیلم , دانلود فیلم با زیرنویس فارسی چسبیده , پخش آنلاین فیلم و سریال , دانلود سریال بدون سانسور , دانلود فیلم جدید , فیلم جدید , فیلم 2 مدیا" yes |
| H1 count | 0 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1 |
| Canonical | https://www.myf2ms.top/ |
| Language | fa-IR |
| Links | 677 |
| Images | 167 |
| 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 myf2m.net is blocked, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | blocked |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
Cloudflare family DNS returned a block for myf2m.net. That resolver covers adult and malware names.
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 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 0 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 aaaa changed from 2a06:98c1:3120::4,2a06:98c1:3121::4 to 2a06:98c1:3120::3,2a06:98c1:3121::3.
Questions
Is myf2m.net safe?
Cloudflare family DNS returned a block for myf2m.net. That resolver covers adult and malware names.
Who hosts myf2m.net?
myf2m.net is placed in Toronto, Canada.
When does myf2m.net expire?
myf2m.net expires on 29 March 2027 according to https://rdap.verisign.com/net/v1/domain/myf2m.net.
Who owns myf2m.net?
The registry did not return a person or a company for myf2m.net. RDAP often redacts the registrant. The registrar on file is TuringSign Inc. d/b/a Cosmotown.
Sources
- RDAP source https://rdap.verisign.com/net/v1/domain/myf2m.net at 2026-10-30T14:54:19Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:54:19Z
- TLS source tls:443 at 2026-10-30T14:54:19Z
- HTTP source https://myf2m.net/ at 2026-10-30T14:54:19Z
- Tech source wappalyzergo at 2026-10-30T14:54:19Z
- Geo source db-ip at 2026-10-30T14:54:19Z
- Safety source family DNS and local lists at 2026-10-30T14:54:19Z
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.