yingfs.me
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafeSSL: 32 days left4 years old
50
yingfs.me was registered on 2 Apr 2022 via Porkbun LLC and the registry expiry is 2 Apr 2027. WHOIS data came from RDAP at https://rdap.identitydigital.services/rdap/domain/yingfs.me.
yingfs.me publishes 4 nameservers. DNSSEC is not signed.
yingfs.me has 1 IPv4 address (177.3.34.243). The geolocation database places 177.3.34.243 in Los Angeles, United States.
The TLS certificate from YR2 is valid and has 32 days left (TLS 1.3).
No safety warning was recorded for yingfs.me in the checks that ran.
Domain · RDAP/WHOIS
yingfs.me was registered on 2 Apr 2022 via Porkbun LLC. The registry returned 2 status values and 4 nameservers from https://rdap.identitydigital.services/rdap/domain/yingfs.me.
| Registered | since 2 Apr 2022 |
|---|---|
| Created | 2 April 2022 |
| Updated | 12 August 2026 |
| Expires | 2 April 2027 |
| Registrar | Porkbun LLC |
| Status | client delete prohibited, client transfer prohibited |
| Nameservers | maceio.ns.porkbun.com, curitiba.ns.porkbun.com, salvador.ns.porkbun.com, fortaleza.ns.porkbun.com |
| DNSSEC | no |
| Source | https://rdap.identitydigital.services/rdap/domain/yingfs.me |
yingfs.me 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.
yingfs.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 maceio.ns.porkbun.com is published for yingfs.me in the registration record from https://rdap.identitydigital.services/rdap/domain/yingfs.me.
Nameserver curitiba.ns.porkbun.com is published for yingfs.me in the registration record from https://rdap.identitydigital.services/rdap/domain/yingfs.me.
Nameserver salvador.ns.porkbun.com is published for yingfs.me in the registration record from https://rdap.identitydigital.services/rdap/domain/yingfs.me.
Nameserver fortaleza.ns.porkbun.com is published for yingfs.me in the registration record from https://rdap.identitydigital.services/rdap/domain/yingfs.me.
DNS
yingfs.me has 1 address record, 0 mail exchangers and 4 nameservers, measured at 1.1.1.1:53.
| A | 177.3.34.243 |
|---|---|
| AAAA | — |
| NS | curitiba.ns.porkbun.com, fortaleza.ns.porkbun.com, maceio.ns.porkbun.com, salvador.ns.porkbun.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 177.3.34.243 answers for yingfs.me at resolver 1.1.1.1:53.
Hosting and geo
yingfs.me is placed in Los Angeles, United States by the local geolocation database (db-ip).
| Address | 177.3.34.243 |
|---|---|
| Country | United States |
| City | Los Angeles |
| Source | db-ip |
SSL/TLS
The certificate for yingfs.me is valid, with 32 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YR2 |
|---|---|
| Subject | www.yingfs.me |
| Valid from | 3 September 2026 |
| Valid until | 2 December 2026 |
| Days left | 32 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: www.yingfs.me, yingfs.me.
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://www.yingfs.cn/": stream error: stream ID 1; PROTOCOL_ERROR; received from peer
Security
Family DNS for yingfs.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 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: rdap created changed from 2022-04-02T15:07:21Z to 2022-04-02T15:07:21.974Z.
- October 2026: rdap dnssec changed from unknown to no.
- October 2026: rdap expires changed from 2027-04-02T15:07:21Z to 2027-04-02T15:07:21.974Z.
- October 2026: rdap statuses changed from clientdeleteprohibited,clienttransferprohibited to client delete prohibited,client transfer prohibited.
- October 2026: rdap updated changed from 2026-08-12T03:45:20Z to 2026-08-12T03:45:20.053Z.
- October 2026: geo city changed from empty to Los Angeles.
- October 2026: geo country changed from empty to United States.
Questions
Is yingfs.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 yingfs.me?
yingfs.me is placed in Los Angeles, United States.
When does yingfs.me expire?
yingfs.me expires on 2 April 2027 according to https://rdap.identitydigital.services/rdap/domain/yingfs.me.
Who owns yingfs.me?
The registry did not return a person or a company for yingfs.me. RDAP often redacts the registrant. The registrar on file is Porkbun LLC.
Sources
- RDAP source https://rdap.identitydigital.services/rdap/domain/yingfs.me at 2026-10-30T14:53:25Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:53:25Z
- TLS source tls:443 at 2026-10-30T14:53:25Z
- HTTP source https://yingfs.me/ at 2026-10-30T14:53:25Z
- Tech source not available at 2026-10-30T14:53:25Z
- Geo source db-ip at 2026-10-30T14:53:25Z
- Safety source family DNS and local lists at 2026-10-30T14:53:25Z
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.