afchina.me
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafeSSL: -1334 days left4 years old
30
afchina.me was registered on 18 Nov 2021 via Spaceship, Inc. and the registry expiry is 18 Nov 2026. WHOIS data came from RDAP at https://rdap.identitydigital.services/rdap/domain/afchina.me.
afchina.me publishes 2 nameservers. DNSSEC is not signed.
afchina.me has 1 IPv4 address (172.96.193.226). The geolocation database places 172.96.193.226 in Los Angeles (Central-Alameda), United States.
The TLS certificate from AlphaSSL CA - SHA256 - G2 is not valid (TLS 1.3).
No safety warning was recorded for afchina.me in the checks that ran.
Domain · RDAP/WHOIS
afchina.me was registered on 18 Nov 2021 via Spaceship, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.identitydigital.services/rdap/domain/afchina.me.
| Registered | since 18 Nov 2021 |
|---|---|
| Created | 18 November 2021 |
| Updated | 12 August 2026 |
| Expires | 18 November 2026 |
| Registrar | Spaceship, Inc. |
| Status | client transfer prohibited |
| Nameservers | jerry.ns.cloudflare.com, rafe.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.identitydigital.services/rdap/domain/afchina.me |
afchina.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 jerry.ns.cloudflare.com is published for afchina.me in the registration record from https://rdap.identitydigital.services/rdap/domain/afchina.me.
Nameserver rafe.ns.cloudflare.com is published for afchina.me in the registration record from https://rdap.identitydigital.services/rdap/domain/afchina.me.
DNS
afchina.me has 1 address record, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 172.96.193.226 |
|---|---|
| AAAA | — |
| NS | jerry.ns.cloudflare.com, rafe.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 172.96.193.226 answers for afchina.me at resolver 1.1.1.1:53.
Hosting and geo
afchina.me is placed in Los Angeles (Central-Alameda), United States by the local geolocation database (db-ip).
| Address | 172.96.193.226 |
|---|---|
| Country | United States |
| City | Los Angeles (Central-Alameda) |
| Source | db-ip |
SSL/TLS
The certificate for afchina.me is not valid, with -1334 days left and 2 subject alternative names. Source: tls:443.
| Issuer | AlphaSSL CA - SHA256 - G2 |
|---|---|
| Subject | *.kgirlimg.xyz |
| Valid from | 2 February 2022 |
| Valid until | 6 March 2023 |
| Days left | -1334 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.kgirlimg.xyz, kgirlimg.xyz.
Validation result: certificate did not validate
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://afchina.me/": tls: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2026-10-30T14:43:35Z is after 2023-03-06T13:15:40Z
Security
Family DNS for afchina.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 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 2021-11-18T14:31:20Z to 2021-11-18T14:31:20.801Z.
- October 2026: rdap dnssec changed from unknown to no.
- October 2026: rdap expires changed from 2026-11-18T14:31:20Z to 2026-11-18T14:31:20.801Z.
- October 2026: rdap statuses changed from clienttransferprohibited to client transfer prohibited.
- October 2026: rdap updated changed from 2026-08-12T08:50:16Z to 2026-08-12T08:50:16.199Z.
- October 2026: geo city changed from empty to Los Angeles (Central-Alameda).
- October 2026: geo country changed from empty to United States.
Questions
Is afchina.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 afchina.me?
afchina.me is placed in Los Angeles (Central-Alameda), United States.
When does afchina.me expire?
afchina.me expires on 18 November 2026 according to https://rdap.identitydigital.services/rdap/domain/afchina.me.
Who owns afchina.me?
The registry did not return a person or a company for afchina.me. RDAP often redacts the registrant. The registrar on file is Spaceship, Inc..
Sources
- RDAP source https://rdap.identitydigital.services/rdap/domain/afchina.me at 2026-10-30T14:43:35Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:43:35Z
- TLS source tls:443 at 2026-10-30T14:43:35Z
- HTTP source https://afchina.me/ at 2026-10-30T14:43:35Z
- Tech source not available at 2026-10-30T14:43:35Z
- Geo source db-ip at 2026-10-30T14:43:35Z
- Safety source family DNS and local lists at 2026-10-30T14:43:35Z
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.