j-ron.dk is a .dk domain served by 2 nameservers (ns1.curanet.dk, ns2.curanet.dk). It was registered on 14 October 2026 (WHOIS) and first appeared in the .dk zone on 15 October 2026. Its website address 212.237.249.16 is hosted by team.blue Denmark A/S (AS48854) in Denmark. Mail is handled by jron-dk0c.mail.protection.outlook.com. The zone is DNSSEC-signed and validates, has no DMARC policy and has no IPv6 address. Below are all of its DNS records from our latest scan: nameservers, A/AAAA, MX, TXT, SPF, DMARC, CAA, TLSA/DANE, MTA-STS, SRV and more.
| IP | TTL | PTR | ASN | ISP / Org | CIDR | Country | City |
|---|---|---|---|---|---|---|---|
| 212.237.249.16 | 3600s | splash.curanet.dk | AS48854 | team.blue Denmark A/S | 212.237.248.0/23 | 🇩🇰 Denmark | — |
| Service | CNAME / IP |
|---|---|
| 🔷 Autodiscover | autodiscover.outlook.com → 52.98.149.152 |
| 🔶 Autoconfig | 212.237.249.16 |
| TXT Record |
|---|
| MS=ms24928266 |
| v=spf1 include:spf.protection.outlook.com -all |
| Policy | Record (j-ron.dk) |
|---|---|
| -all (hard fail) | v=spf1 include:spf.protection.outlook.com -all |
| www | 212.237.249.16 (AS48854) (address records, no CNAME) |
| www vs bare domain | Same network |
| Wildcard | Yes: any name under the zone resolves |
| Denial of existence | NSEC3 · 1 iteration · 1-byte salt RFC 9276 recommends 0 iterations and no salt |
| CDS / CDNSKEY | None 0 CDS, 0 CDNSKEY |
DNS lookups: 1/10 · policy: -all
No problems found| Check | Result |
|---|---|
| Validation Status | 🔒 Secure |
| AD Flag (resolver validates) | ✓ Set |
| DS Record | ✓ Found |
| DNSKEY Record | ✓ Found |
| Flags | fully validated |
| Field | Value |
|---|---|
| Serial | 2026101406 |
| Primary NS (MNAME) | ns1.curanet.dk |
| Responsible (RNAME) | hostmaster@curanet.dk |
| Refresh | 14400s |
| Retry | 3600s |
| Expire | 1209600s |
| Minimum (neg-cache TTL) | 300s |
| Field | Value |
|---|---|
| Registrar | CURANET A/S |
| Registered | 2026-10-14 |
| Expires | 2027-10-13 (360d) |
Other .dk domains whose WHOIS registrant has the same name and postal address. Matched on a keyed hash: the registrant's details are not stored or shown. Covers only domains whose WHOIS we have fetched (refreshed about monthly).