yinfans.me
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafe7 years oldTranco #923994
35
yinfans.me was registered on 25 Mar 2019 via NameCheap, Inc. and the registry expiry is 25 Mar 2028. WHOIS data came from RDAP at https://rdap.identitydigital.services/rdap/domain/yinfans.me.
yinfans.me publishes 2 nameservers. DNSSEC is not signed.
No safety warning was recorded for yinfans.me in the checks that ran.
Domain · RDAP/WHOIS
yinfans.me was registered on 25 Mar 2019 via NameCheap, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.identitydigital.services/rdap/domain/yinfans.me.
| Registered | since 25 Mar 2019 |
|---|---|
| Created | 25 March 2019 |
| Updated | 12 August 2026 |
| Expires | 25 March 2028 |
| Registrar | NameCheap, Inc. |
| Status | client transfer prohibited |
| Nameservers | odin.ns.cloudflare.com, angelina.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.identitydigital.services/rdap/domain/yinfans.me |
yinfans.me 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 odin.ns.cloudflare.com is published for yinfans.me in the registration record from https://rdap.identitydigital.services/rdap/domain/yinfans.me.
Nameserver angelina.ns.cloudflare.com is published for yinfans.me in the registration record from https://rdap.identitydigital.services/rdap/domain/yinfans.me.
DNS
yinfans.me has 0 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | — |
|---|---|
| AAAA | — |
| NS | angelina.ns.cloudflare.com, odin.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The DMARC text record at _dmarc.yinfans.me is "v=DMARC1;p=quarantine;rua=mailto:[email protected]".
Hosting and geo
Geolocation for yinfans.me is not available. No local city or ASN database is installed, so this report does not guess a country.
| Geolocation | not available |
|---|---|
| Source | maxmind |
SSL/TLS
No TLS certificate was read for yinfans.me on port 443.
| Available | no |
|---|---|
| Source | tls:443 |
dial tcp: lookup yinfans.me on 46.38.252.230:53: no such host
Tech stack
Tech detection did not run.
| Checked | no |
|---|---|
| Source | wappalyzergo |
On-page checks
The homepage fetch did not return a status code.
| Status | none |
|---|
Get "https://yinfans.me/": dial tcp: lookup yinfans.me on 46.38.252.230:53: no such host
Security
Family DNS for yinfans.me 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 0 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: rdap created changed from 2019-03-25T03:28:19Z to 2019-03-25T03:28:19.912Z.
- October 2026: rdap dnssec changed from unknown to no.
- October 2026: rdap expires changed from 2028-03-25T03:28:19Z to 2028-03-25T03:28:19.912Z.
- October 2026: rdap statuses changed from clienttransferprohibited to client transfer prohibited.
- October 2026: rdap updated changed from 2026-08-12T06:51:17Z to 2026-08-12T06:51:17.197Z.
Questions
Is yinfans.me 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 yinfans.me?
The host network is not available without a local geolocation database.
When does yinfans.me expire?
yinfans.me expires on 25 March 2028 according to https://rdap.identitydigital.services/rdap/domain/yinfans.me.
Who owns yinfans.me?
The registry did not return a person or a company for yinfans.me. RDAP often redacts the registrant. The registrar on file is NameCheap, Inc..
Sources
- RDAP source https://rdap.identitydigital.services/rdap/domain/yinfans.me at 2026-10-30T14:53:23Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:53:23Z
- TLS source tls:443 at 2026-10-30T14:53:23Z
- HTTP source https://yinfans.me/ at 2026-10-30T14:53:23Z
- Tech source not available at 2026-10-30T14:53:23Z
- Geo source db-ip at 2026-10-30T14:53:23Z
- Safety source family DNS and local lists at 2026-10-30T14:53:23Z
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.