mingky.net
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
HTTP 403Family DNS blockedSSL: 80 days left14 years old
40
mingky.net was registered on 28 Nov 2011 via NameCheap, Inc. and the registry expiry is 28 Nov 2027. WHOIS data came from RDAP at https://rdap.verisign.com/net/v1/domain/mingky.net.
mingky.net publishes 2 nameservers. DNSSEC is not signed.
mingky.net has 1 IPv4 address (158.247.216.108). The geolocation database places 158.247.216.108 in Mapo-gu, South Korea.
The TLS certificate from YR1 is valid and has 80 days left (TLS 1.3).
Tech detection named Cloudflare and HTTP/3. The fingerprints ran on the homepage that was already downloaded.
Domain · RDAP/WHOIS
mingky.net was registered on 28 Nov 2011 via NameCheap, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/net/v1/domain/mingky.net.
| Registered | since 28 Nov 2011 |
|---|---|
| Created | 28 November 2011 |
| Updated | 5 May 2026 |
| Expires | 28 November 2027 |
| Registrar | NameCheap, Inc. |
| Status | client transfer prohibited |
| Nameservers | jose.ns.cloudflare.com, serenity.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/net/v1/domain/mingky.net |
mingky.net 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 jose.ns.cloudflare.com is published for mingky.net in the registration record from https://rdap.verisign.com/net/v1/domain/mingky.net.
Nameserver serenity.ns.cloudflare.com is published for mingky.net in the registration record from https://rdap.verisign.com/net/v1/domain/mingky.net.
DNS
mingky.net has 1 address record, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 158.247.216.108 |
|---|---|
| AAAA | — |
| NS | jose.ns.cloudflare.com, serenity.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 158.247.216.108 answers for mingky.net at resolver 1.1.1.1:53.
Hosting and geo
mingky.net is placed in Mapo-gu, South Korea by the local geolocation database (db-ip).
| Address | 158.247.216.108 |
|---|---|
| Country | South Korea |
| City | Mapo-gu |
| Source | db-ip |
SSL/TLS
The certificate for mingky.net is valid, with 80 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YR1 |
|---|---|
| Subject | mingky.net |
| Valid from | 22 October 2026 |
| Valid until | 20 January 2027 |
| Days left | 80 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: mingky.net, www.mingky.net.
Tech stack
Tech detection checked the fetched homepage and named 2 products. Source: wappalyzergo.
- Cloudflare · CDN
- HTTP/3 · Miscellaneous
Cloudflare is filed under CDN.
HTTP/3 is filed under Miscellaneous.
On-page checks
The homepage returned HTTP 403 in 281 ms. The target title is 32 characters and the page has 1 H1 heading.
| Status | 403 |
|---|---|
| TTFB | 281 ms |
| Title length | 32 yes |
| Quoted title | "Attention Required! | Cloudflare" |
| Meta description | none no |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | noindex, nofollow |
| Canonical | — |
| Language | en-US |
| Links | 1 |
| Images | 0 |
| 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 mingky.net 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 mingky.net. 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.
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 5 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.
Change history
- October 2026: geo city changed from empty to Mapo-gu.
- October 2026: geo country changed from empty to South Korea.
Questions
Is mingky.net safe?
Cloudflare family DNS returned a block for mingky.net. That resolver covers adult and malware names.
Who hosts mingky.net?
mingky.net is placed in Mapo-gu, South Korea.
When does mingky.net expire?
mingky.net expires on 28 November 2027 according to https://rdap.verisign.com/net/v1/domain/mingky.net.
Who owns mingky.net?
The registry did not return a person or a company for mingky.net. RDAP often redacts the registrant. The registrar on file is NameCheap, Inc..
Sources
- RDAP source https://rdap.verisign.com/net/v1/domain/mingky.net at 2026-10-30T14:54:01Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:54:01Z
- TLS source tls:443 at 2026-10-30T14:54:01Z
- HTTP source https://mingky.net/ at 2026-10-30T14:54:01Z
- Tech source wappalyzergo at 2026-10-30T14:54:01Z
- Geo source db-ip at 2026-10-30T14:54:01Z
- Safety source family DNS and local lists at 2026-10-30T14:54:01Z
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.