xingxi.xyz
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
70
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
70
xingxi.xyz was registered on 9 Sep 2019 via NameSilo, LLC and the registry expiry is 9 Sep 2027. WHOIS data came from RDAP at https://rdap.centralnic.com/xyz/domain/xingxi.xyz.
xingxi.xyz publishes 2 nameservers. DNSSEC is not signed.
xingxi.xyz has 2 IPv4 addresses (104.21.14.232, 172.67.160.192). The geolocation database places 104.21.14.232 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 57 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Bootstrap, Cloudflare, HTTP/3, Microsoft ASP.NET and jQuery. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for xingxi.xyz in the checks that ran.
xingxi.xyz was registered on 9 Sep 2019 via NameSilo, LLC. The registry returned 1 status value and 2 nameservers from https://rdap.centralnic.com/xyz/domain/xingxi.xyz.
| Registered | since 9 Sep 2019 |
|---|---|
| Created | 9 September 2019 |
| Updated | 10 September 2026 |
| Expires | 9 September 2027 |
| Registrar | NameSilo, LLC |
| Status | client transfer prohibited |
| Nameservers | melinda.ns.cloudflare.com, rick.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.centralnic.com/xyz/domain/xingxi.xyz |
xingxi.xyz 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 melinda.ns.cloudflare.com is published for xingxi.xyz in the registration record from https://rdap.centralnic.com/xyz/domain/xingxi.xyz.
Nameserver rick.ns.cloudflare.com is published for xingxi.xyz in the registration record from https://rdap.centralnic.com/xyz/domain/xingxi.xyz.
xingxi.xyz has 2 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.14.232, 172.67.160.192 |
|---|---|
| AAAA | — |
| NS | melinda.ns.cloudflare.com, rick.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | issue comodoca.com, issue digicert.com; cansignhttpexchanges=yes, issue letsencrypt.org, issue pki.goog; cansignhttpexchanges=yes, issue ssl.com, issuewild comodoca.com, issuewild digicert.com; cansignhttpexchanges=yes, issuewild letsencrypt.org, issuewild pki.goog; cansignhttpexchanges=yes, issuewild ssl.com |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 104.21.14.232 answers for xingxi.xyz at resolver 1.1.1.1:53.
IPv4 address 172.67.160.192 answers for xingxi.xyz at resolver 1.1.1.1:53.
xingxi.xyz is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.14.232 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
The certificate for xingxi.xyz is valid, with 57 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | xingxi.xyz |
| Valid from | 29 September 2026 |
| Valid until | 28 December 2026 |
| Days left | 57 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.xingxi.xyz, xingxi.xyz.
Tech detection checked the fetched homepage and named 5 products. Source: wappalyzergo.
Bootstrap is filed under UI frameworks.
Cloudflare is filed under CDN.
HTTP/3 is filed under Miscellaneous.
Microsoft ASP.NET is filed under Web frameworks.
jQuery is filed under JavaScript libraries.
The homepage returned HTTP 200 in 151 ms. The target title is 25 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 151 ms |
| Title length | 25 yes |
| Quoted title | "凤楼阁论坛-全国楼凤论坛免费,男人的信息分享平台." |
| Meta description | "凤楼阁论坛,自由开放,信息共享,这里有全国各地楼凤,兼职,良家,桑拿,洗浴,按摩,会所,高端外围及体验感受的详细性息介绍,全国楼凤论坛免费" yes |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | zh-CN |
| Links | 163 |
| Images | 27 |
| Favicon | yes |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Family DNS for xingxi.xyz 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.
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 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.
First checked on 30 October 2026; changes will appear here.
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
xingxi.xyz is placed in Toronto, Canada.
xingxi.xyz expires on 9 September 2027 according to https://rdap.centralnic.com/xyz/domain/xingxi.xyz.
The registry did not return a person or a company for xingxi.xyz. RDAP often redacts the registrant. The registrar on file is NameSilo, LLC.
No other indexable reports share this TLD, host, or registrar yet.
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.
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.