mandatoryprogrammer/NorthKoreaDNSLeak resource
Snapshot of North Korea's DNS data taken from zone transfers. observed · 2026-08-28
Health v2 · maintenance only
32/100
- Activity 0
- Release rhythm 35
- Longevity 100
Flags: no_releases no_license
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 3634
- days_rel: n/a
- days_push: 3631
- n_releases_24m: 0
Adoption not part of the score
1751 stars · 208 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
A snapshot of North Korea's .kp top-level domain DNS zone data, obtained via an accidental AXFR zone transfer from the ns2.kptc.kp nameserver in September 2016. It is a static dataset documenting the country's DNS records and domain inventory.
Use cases
- research north korea's internet infrastructure
- analyze .kp domain names and DNS records
- study DNS zone transfer vulnerabilities
- historical snapshot of north korean domains
- osint research on north korean networks
When to choose
- you need historical .kp DNS data for research or OSINT analysis
- you want an example of DNS zone transfer misconfiguration consequences
When to avoid
- you need current or live DNS data for .kp domains
- you need a tool rather than a static dataset
- you need actively maintained data
Facets
dataset · maturity abandoned
networking security osint security networking osint cross-platform dns zone-transfer north-korea axfr dns-data tld
1 source
- readme: https://github.com/mandatoryprogrammer/NorthKoreaDNSLeak · fetched 2026-08-28 · 0826106b07a1
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| mandatoryprogrammer/NorthKoreaDNSLeak | main | 32 |
For agents
markdown · JSON · MCP: product_card(name="mandatoryprogrammer/NorthKoreaDNSLeak")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem