dessertdragen.dk
dessertdragen.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 4 November 2026 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. We saw it become registrar-handled on 5 November 2026, when it moved from direct registration at Punktum to Ilkari Domains Limited. 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.
Nameservers#
2 records 155msA Records#
MX Records#
AAAA Records (IPv6)#
HTTPS Records#
TXT Records#
SPF#
DMARC#
MTA-STS#
TLSRPT#
CAA Records#
Web & zone#
latest probe, not this scan · checked 2026-11-09 08:39:49| www | 104.21.89.124 172.67.159.84 2606:4700:3034::6815:597c 2606:4700:3034::ac43:9f54 (AS13335) (address records, no CNAME) |
| www vs bare domain | Same network dessertdragen.dk: 104.21.89.124 172.67.159.84 2606:4700:3034::6815:597c 2606:4700:3034::ac43:9f54 (AS13335) www.dessertdragen.dk: 104.21.89.124 172.67.159.84 2606:4700:3034::6815:597c 2606:4700:3034::ac43:9f54 (AS13335) |
| Wildcard | No |
TLSA / DANE#
DNSSEC#
298ms| Check | Result |
|---|---|
| Validation Status | Bogus — the parent still publishes a DS record, but the delegated nameservers don't answer, so no signed answer can be fetched. The zone isn't serving broken signatures; it isn't serving at all. |
| AD Flag (resolver validates) | Not set |
| DS Record | Found |
| DNSKEY Record | Not found |
| Flags | resolution failed: failure |
SOA#
Registration#
WHOIS fetched 2026-11-09 09:08:39| Field | Value |
|---|---|
| Registrar | Ilkari Domains Limited |
| Registered | 2026-11-04 |
| Expires | 2027-11-03 (349d) |
Same registrant#
598 domainsOther .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).
Showing 100 of 598.
Lookup Timing#
Scan History#
| Scanned At | Duration | Records | DNSSEC |
|---|---|---|---|
| 2026-11-09 08:39:49 | 882ms | 2 NS 2 A 0 MX | Insecure |
| 2026-11-08 08:37:48 | 1463ms | 2 NS 1 A 0 MX | Insecure |
| 2026-11-07 08:35:29 | 1043ms | 2 NS 1 A 0 MX | Insecure |
| 2026-11-06 08:33:53 | 973ms | 2 NS 1 A 0 MX | Insecure |
| 2026-11-05 08:33:06 | 1064ms | 2 NS 1 A 0 MX | Insecure |
| 2026-09-23 08:27:53 | 35103ms | 2 NS 0 A 0 MX | Unknown |
| 2026-09-11 14:51:33 shown | 45155ms | 2 NS 0 A 0 MX | Bogus |
| 2026-09-07 23:59:15 | 835ms | 2 NS 1 A 4 MX | Secure |
| 2026-08-26 16:33:32 | 822ms | 2 NS 1 A 4 MX | Secure |
| 2026-08-25 16:30:43 | 706ms | 2 NS 1 A 4 MX | Secure |
| 2026-07-26 16:04:13 | 6923ms | 2 NS 1 A 4 MX | Secure |
| 2026-06-24 13:35:10 | 1243ms | 2 NS 1 A 4 MX | Secure |
| 2026-06-22 13:50:15 | 1182ms | 0 NS 0 A 0 MX | Unknown |
| 2026-06-20 07:20:46 | 899ms | 2 NS 1 A 4 MX | Secure |
| 2026-06-19 17:32:28 | 1087ms | 2 NS 1 A 4 MX | Secure |
| 2026-06-17 02:15:51 | 703ms | 2 NS 1 A 4 MX | Secure |