maglemer.dk
Historical scan 2026-07-03 00:16:12 · ← Latest scan
maglemer.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 2 October 2004 (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.
Nameservers#
2 records 4039msA Records#
No A records found
MX Records#
No MX records found
AAAA Records (IPv6)#
No AAAA records — IPv6 not configured
HTTPS Records#
No HTTPS RR — no SVCB/HTTPS service binding
TXT Records#
No TXT records found
SPF#
No SPF record — mail spoofing not restricted
DMARC#
No DMARC record — mail spoofing not restricted
MTA-STS#
No MTA-STS policy — SMTP TLS not enforced
TLSRPT#
No TLSRPT record — no SMTP TLS failure reporting
CAA Records#
No CAA records — any CA may issue certificates
Web & zone#
latest probe, not this scan · checked 2026-10-29 04:12:00| www | 46.30.215.40 2a02:2350:5:10e:8045:3a35:3287:4180 (AS51468) (address records, no CNAME) |
| www vs bare domain | Same network maglemer.dk: 46.30.215.40 2a02:2350:5:10e:8045:3a35:3287:4180 (AS51468) www.maglemer.dk: 46.30.215.40 2a02:2350:5:10e:8045:3a35:3287:4180 (AS51468) |
| Wildcard | No |
| Denial of existence | NSEC3 · 0 iterations · no salt RFC 9276 ✓ |
| CDS / CDNSKEY | None 0 CDS, 0 CDNSKEY |
TLSA / DANE#
No TLSA records — DANE not configured for HTTPS (_443) or MX (_25)
DNSSEC#
10171ms| 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: timed out |
SOA#
No SOA record found
Registration#
WHOIS fetched 2026-10-20 16:38:21| Field | Value |
|---|---|
| Registrar | Punktum dk A/S (direct) |
| Registered | 2004-10-02 |
| Expires | 2027-10-31 (347d) |
Same registrant#
0 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).
No other domain with this registrant in our WHOIS data yet
📋 WHOIS#
Lookup Timing#
NS
A
MX
AAAA
TXT
CAA
HTTPS
TLSA
SOA
MTA-STS
DNSSEC
SRV
Total
Scan History#
| Scanned At | Duration | Records | DNSSEC |
|---|---|---|---|
| 2026-10-29 04:12:00 | 537ms | 2 NS 1 A 3 MX | Secure |
| 2026-10-27 10:59:09 | 607ms | 2 NS 1 A 3 MX | Secure |
| 2026-10-24 15:13:46 | 1416ms | 2 NS 1 A 3 MX | Secure |
| 2026-10-02 18:08:09 | 481ms | 2 NS 1 A 3 MX | Secure |
| 2026-10-01 06:07:00 | 526ms | 2 NS 1 A 3 MX | Secure |
| 2026-09-30 02:45:16 | 463ms | 2 NS 1 A 3 MX | Secure |
| 2026-09-28 06:50:54 | 686ms | 2 NS 1 A 3 MX | Secure |
| 2026-09-24 01:53:30 | 635ms | 2 NS 1 A 3 MX | Secure |
| 2026-09-12 04:53:31 | 529ms | 2 NS 1 A 3 MX | Secure |
| 2026-08-24 13:20:29 | 2491ms | 2 NS 1 A 3 MX | Secure |
| 2026-08-18 09:09:22 | 4916ms | 2 NS 1 A 3 MX | Secure |
| 2026-07-24 21:16:11 | 1053ms | 2 NS 1 A 3 MX | Secure |
| 2026-07-03 00:16:12 shown | 13236ms | 2 NS 0 A 0 MX | Unknown |
| 2026-06-27 19:35:38 | 6007ms | 2 NS 1 A 3 MX | Secure |
| 2026-06-25 09:20:23 | 719ms | 2 NS 1 A 3 MX | Secure |
| 2026-06-23 15:17:35 | 902ms | 0 NS 0 A 0 MX | Unknown |
| 2026-06-23 03:01:13 | 676ms | 2 NS 1 A 3 MX | Secure |
| 2026-06-17 22:47:23 | 969ms | 2 NS 1 A 3 MX | Secure |