cupfox.app
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
50
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
50
cupfox.app was registered on 15 Nov 2021 via Porkbun LLC and the registry expiry is 15 Nov 2026. WHOIS data came from RDAP at https://pubapi.registry.google/rdap/domain/cupfox.app.
cupfox.app publishes 2 nameservers. DNSSEC is not signed.
cupfox.app has 2 IPv4 addresses (188.114.96.3, 188.114.97.3) and 2 IPv6 addresses (2a06:98c1:3120::4, 2a06:98c1:3121::4). The geolocation database places 188.114.96.3 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 67 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, Google AdSense, HTTP/3, Next.js, Node.js, React and Webpack. The fingerprints ran on the homepage that was already downloaded.
cupfox.app was registered on 15 Nov 2021 via Porkbun LLC. The registry returned 2 status values and 2 nameservers from https://pubapi.registry.google/rdap/domain/cupfox.app.
| Registered | since 15 Nov 2021 |
|---|---|
| Created | 15 November 2021 |
| Updated | 3 June 2026 |
| Expires | 15 November 2026 |
| Registrar | Porkbun LLC |
| Status | client delete prohibited, client transfer prohibited |
| Nameservers | jillian.ns.cloudflare.com, melnicoff.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://pubapi.registry.google/rdap/domain/cupfox.app |
cupfox.app 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.
cupfox.app 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 jillian.ns.cloudflare.com is published for cupfox.app in the registration record from https://pubapi.registry.google/rdap/domain/cupfox.app.
Nameserver melnicoff.ns.cloudflare.com is published for cupfox.app in the registration record from https://pubapi.registry.google/rdap/domain/cupfox.app.
cupfox.app has 4 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 188.114.96.3, 188.114.97.3 |
|---|---|
| AAAA | 2a06:98c1:3120::4, 2a06:98c1:3121::4 |
| NS | jillian.ns.cloudflare.com, melnicoff.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 188.114.96.3 answers for cupfox.app at resolver 1.1.1.1:53.
IPv4 address 188.114.97.3 answers for cupfox.app at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3120::4 answers for cupfox.app at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3121::4 answers for cupfox.app at resolver 1.1.1.1:53.
cupfox.app is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 188.114.96.3 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
The certificate for cupfox.app is valid, with 67 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | cupfox.app |
| Valid from | 8 October 2026 |
| Valid until | 6 January 2027 |
| Days left | 67 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.cupfox.app, cupfox.app.
Tech detection checked the fetched homepage and named 7 products. Source: wappalyzergo.
Cloudflare is filed under CDN.
Google AdSense is filed under Advertising.
HTTP/3 is filed under Miscellaneous.
Next.js is filed under JavaScript frameworks, Web frameworks.
Node.js is filed under Programming languages.
React is filed under JavaScript frameworks.
Webpack is filed under Miscellaneous.
The homepage returned HTTP 200 in 614 ms. The target title is 15 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 614 ms |
| Title length | 15 yes |
| Quoted title | "茶杯狐 - 片荒剧荒就来茶杯狐" |
| Meta description | "最新片单请微信搜索关注“茶杯狐”公众号!" yes |
| H1 count | 0 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | zh-CN |
| Links | 89 |
| Images | 68 |
| 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 cupfox.app is blocked, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | blocked |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
Cloudflare family DNS returned a block for cupfox.app. That resolver covers adult and malware names.
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 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 0 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.
Cloudflare family DNS returned a block for cupfox.app. That resolver covers adult and malware names.
cupfox.app is placed in Toronto, Canada.
cupfox.app expires on 15 November 2026 according to https://pubapi.registry.google/rdap/domain/cupfox.app.
The registry did not return a person or a company for cupfox.app. RDAP often redacts the registrant. The registrar on file is Porkbun 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.