dujiza.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 47 days left16 years oldTranco #656699
65
dujiza.com was registered on 30 Dec 2009 via Alibaba Cloud Computing (Beijing) Co., Ltd. and the registry expiry is 30 Dec 2035. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/dujiza.com.
dujiza.com publishes 2 nameservers. DNSSEC is not signed.
dujiza.com has 1 IPv4 address (8.217.248.30). The geolocation database places 8.217.248.30 in Hong Kong, Hong Kong.
The TLS certificate from YE2 is valid and has 47 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Apache HTTP Server and jQuery. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for dujiza.com in the checks that ran.
Domain · RDAP/WHOIS
dujiza.com was registered on 30 Dec 2009 via Alibaba Cloud Computing (Beijing) Co., Ltd.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/dujiza.com.
| Registered | since 30 Dec 2009 |
|---|---|
| Created | 30 December 2009 |
| Updated | 23 July 2026 |
| Expires | 30 December 2035 |
| Registrar | Alibaba Cloud Computing (Beijing) Co., Ltd. |
| Status | active |
| Nameservers | vip3.alidns.com, vip4.alidns.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/dujiza.com |
Nameserver vip3.alidns.com is published for dujiza.com in the registration record from https://rdap.verisign.com/com/v1/domain/dujiza.com.
Nameserver vip4.alidns.com is published for dujiza.com in the registration record from https://rdap.verisign.com/com/v1/domain/dujiza.com.
DNS
dujiza.com has 1 address record, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 8.217.248.30 |
|---|---|
| AAAA | — |
| NS | vip3.alidns.com, vip4.alidns.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 8.217.248.30 answers for dujiza.com at resolver 1.1.1.1:53.
Hosting and geo
dujiza.com is placed in Hong Kong, Hong Kong by the local geolocation database (db-ip).
| Address | 8.217.248.30 |
|---|---|
| Country | Hong Kong |
| City | Hong Kong |
| Source | db-ip |
SSL/TLS
The certificate for dujiza.com is valid, with 47 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YE2 |
|---|---|
| Subject | dujiza.com |
| Valid from | 19 September 2026 |
| Valid until | 18 December 2026 |
| Days left | 47 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: dujiza.com, www.dujiza.com.
Tech stack
Tech detection checked the fetched homepage and named 2 products. Source: wappalyzergo.
- Apache HTTP Server · Web servers
- jQuery · JavaScript libraries
Apache HTTP Server is filed under Web servers.
jQuery is filed under JavaScript libraries.
On-page checks
The homepage returned HTTP 200 in 258 ms. The target title is 23 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 258 ms |
| Title length | 23 yes |
| Quoted title | "朝鲜族网址站-朝鲜语网站 dujiza.com" |
| Meta description | "专门为中国的朝鲜民族制作的网站" yes |
| H1 count | 0 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | — |
| Links | 290 |
| Images | 1 |
| Favicon | no |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Security
Family DNS for dujiza.com 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 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 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: geo city changed from empty to Hong Kong.
- October 2026: geo country changed from empty to Hong Kong.
Questions
Is dujiza.com 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 dujiza.com?
dujiza.com is placed in Hong Kong, Hong Kong.
When does dujiza.com expire?
dujiza.com expires on 30 December 2035 according to https://rdap.verisign.com/com/v1/domain/dujiza.com.
Who owns dujiza.com?
The registry did not return a person or a company for dujiza.com. RDAP often redacts the registrant. The registrar on file is Alibaba Cloud Computing (Beijing) Co., Ltd..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/dujiza.com at 2026-10-30T13:52:23Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:52:23Z
- TLS source tls:443 at 2026-10-30T13:52:23Z
- HTTP source https://dujiza.com/ at 2026-10-30T13:52:23Z
- Tech source wappalyzergo at 2026-10-30T13:52:23Z
- Geo source db-ip at 2026-10-30T13:52:23Z
- Safety source family DNS and local lists at 2026-10-30T13:52: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.