bodilegeberg.dk is a registered .dk domain whose nameservers (ns01.one.com, ns02.one.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 27 November 2007 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. Below are all of its DNS records from this scan: nameservers, A/AAAA, MX, TXT, SPF, DMARC, CAA, TLSA/DANE, MTA-STS, SRV and more.
| www | 77.111.240.142 2a02:2350:5:102:72:b764:b3c4:7ec6 (AS51468) (address records, no CNAME) |
| www vs bare domain | Same network bodilegeberg.dk: 77.111.240.142 2a02:2350:5:102:72:b764:b3c4:7ec6 (AS51468) www.bodilegeberg.dk: 77.111.240.142 2a02:2350:5:102:72:b764:b3c4:7ec6 (AS51468) |
| Wildcard | No |
| Denial of existence | NSEC3 · 0 iterations · no salt RFC 9276 ✓ |
| CDS / CDNSKEY | None 0 CDS, 0 CDNSKEY |
| Check | Result |
|---|---|
| Validation Status | ❓ Unknown (the delegated nameservers don't answer) |
| AD Flag (resolver validates) | ✗ Not set |
| DS Record | ✓ Found |
| DNSKEY Record | ✗ Not found |
| Flags | resolution failed: failure |
| Field | Value |
|---|---|
| Registrar | ONE.COM A/S |
| Registered | 2007-11-27 |
| Expires | 2026-11-30 (43d) |
| Scanned At | Duration | Records | DNSSEC |
|---|---|---|---|
| 2026-10-03 17:32:20 | 503ms | 2 NS 1 A 4 MX | 🔒 Secure |
| 2026-09-30 20:51:22 | 1664ms | 2 NS 1 A 4 MX | 🔒 Secure |
| 2026-09-19 03:04:51 | 718ms | 2 NS 1 A 4 MX | 🔒 Secure |
| 2026-09-01 01:51:53 | 614ms | 2 NS 1 A 4 MX | 🔒 Secure |
| 2026-08-26 04:38:00 | 1136ms | 2 NS 1 A 4 MX | 🔒 Secure |
| 2026-07-31 05:10:11 | 1090ms | 2 NS 1 A 4 MX | 🔒 Secure |
| 2026-07-21 02:37:02 | 1009ms | 2 NS 1 A 4 MX | 🔒 Secure |
| 2026-07-06 07:07:09 | 4466ms | 2 NS 1 A 4 MX | 🔒 Secure |
| 2026-07-04 02:11:51 | 8330ms | 2 NS 1 A 4 MX | 🔒 Secure |
| 2026-07-03 22:49:52 | 26304ms | 2 NS 0 A 0 MX | ❓ Unknown |
| 2026-07-03 01:19:23 shown | 22324ms | 2 NS 0 A 0 MX | ❓ Unknown |
| 2026-07-02 23:46:16 | 817ms | 2 NS 1 A 4 MX | 🔒 Secure |
| 2026-06-22 22:22:41 | 846ms | 2 NS 1 A 4 MX | 🔒 Secure |
| 2026-06-20 11:03:54 | 520ms | 2 NS 1 A 4 MX | 🔒 Secure |
| 2026-06-16 15:26:09 | 568ms | 2 NS 1 A 4 MX | 🔒 Secure |
| 2026-06-16 15:20:25 | 741ms | 2 NS 1 A 4 MX | 🔒 Secure |