fenxm.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 74 days left4 years old
70
fenxm.com was registered on 9 Mar 2022 via Alibaba Cloud Computing Ltd. d/b/a HiChina (www.net.cn) and the registry expiry is 9 Mar 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/fenxm.com.
fenxm.com publishes 2 nameservers. DNSSEC is not signed.
fenxm.com has 1 IPv4 address (101.37.71.11). The geolocation database places 101.37.71.11 in Hangzhou, China.
The TLS certificate from TrustAsia DV TLS RSA CA 2024 is valid and has 74 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Google AdSense, HSTS, HTTP/3, Nginx and jQuery. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for fenxm.com in the checks that ran.
Domain · RDAP/WHOIS
fenxm.com was registered on 9 Mar 2022 via Alibaba Cloud Computing Ltd. d/b/a HiChina (www.net.cn). The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/fenxm.com.
| Registered | since 9 Mar 2022 |
|---|---|
| Created | 9 March 2022 |
| Updated | 11 February 2026 |
| Expires | 9 March 2027 |
| Registrar | Alibaba Cloud Computing Ltd. d/b/a HiChina (www.net.cn) |
| Status | active |
| Nameservers | vip1.alidns.com, vip2.alidns.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/fenxm.com |
Nameserver vip1.alidns.com is published for fenxm.com in the registration record from https://rdap.verisign.com/com/v1/domain/fenxm.com.
Nameserver vip2.alidns.com is published for fenxm.com in the registration record from https://rdap.verisign.com/com/v1/domain/fenxm.com.
DNS
fenxm.com has 1 address record, 2 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 101.37.71.11 |
|---|---|
| AAAA | — |
| NS | vip1.alidns.com, vip2.alidns.com |
| MX | mxn.mxhichina.com (5), mxw.mxhichina.com (10) |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 101.37.71.11 answers for fenxm.com at resolver 1.1.1.1:53.
Mail exchanger mxn.mxhichina.com has preference 5.
Mail exchanger mxw.mxhichina.com has preference 10.
Hosting and geo
fenxm.com is placed in Hangzhou, China by the local geolocation database (db-ip).
| Address | 101.37.71.11 |
|---|---|
| Country | China |
| City | Hangzhou |
| Source | db-ip |
SSL/TLS
The certificate for fenxm.com is valid, with 74 days left and 2 subject alternative names. Source: tls:443.
| Issuer | TrustAsia DV TLS RSA CA 2024 |
|---|---|
| Subject | fenxm.com |
| Valid from | 16 October 2026 |
| Valid until | 14 January 2027 |
| Days left | 74 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: fenxm.com, www.fenxm.com.
Tech stack
Tech detection checked the fetched homepage and named 5 products. Source: wappalyzergo.
- Google AdSense · Advertising
- HSTS · Security
- HTTP/3 · Miscellaneous
- Nginx · Web servers, Reverse proxies
- jQuery · JavaScript libraries
Google AdSense is filed under Advertising.
HSTS is filed under Security.
HTTP/3 is filed under Miscellaneous.
Nginx is filed under Web servers, Reverse proxies.
jQuery is filed under JavaScript libraries.
On-page checks
The homepage returned HTTP 200 in 811 ms. The target title is 11 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 811 ms |
| Title length | 11 yes |
| Quoted title | "分享迷 - 痴迷分享！" |
| Meta description | "分享迷致力于优质精品TV软件、技术教程、绿色软件、系统工具、效率应用与科技资讯分享，长期更新，痴迷分享互联网上一切美好事物！" yes |
| H1 count | 1 |
| HSTS | yes yes |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | https://www.fenxm.com/ |
| Language | zh-Hans |
| Links | 129 |
| Images | 33 |
| Favicon | yes |
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 fenxm.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 | yes |
| 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 0 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.
Change history
- October 2026: geo city changed from empty to Hangzhou.
- October 2026: geo country changed from empty to China.
Questions
Is fenxm.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 fenxm.com?
fenxm.com is placed in Hangzhou, China.
When does fenxm.com expire?
fenxm.com expires on 9 March 2027 according to https://rdap.verisign.com/com/v1/domain/fenxm.com.
Who owns fenxm.com?
The registry did not return a person or a company for fenxm.com. RDAP often redacts the registrant. The registrar on file is Alibaba Cloud Computing Ltd. d/b/a HiChina (www.net.cn).
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/fenxm.com at 2026-10-30T13:54:31Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:54:31Z
- TLS source tls:443 at 2026-10-30T13:54:31Z
- HTTP source https://fenxm.com/ at 2026-10-30T13:54:31Z
- Tech source wappalyzergo at 2026-10-30T13:54:31Z
- Geo source db-ip at 2026-10-30T13:54:31Z
- Safety source family DNS and local lists at 2026-10-30T13:54:31Z
Related reports
No other indexable reports share this TLD, host, or registrar yet.
.com Alibaba Cloud Computing Ltd. d/b/a HiChina (www.net.cn)
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.