amager2300.dk

Records from scan: 2026-10-25 02:23:26  ·  1217ms total  ·  last checked 2026-11-21 04:34 (unchanged)
Lame delegation Zone File Timeline & History

amager2300.dk is a registered .dk domain whose nameservers (ns1.simply.com, ns2.simply.com, ns3.simply.com and 1 more) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 20 August 2018 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. 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.

Nameservers#

4 records   91ms

A 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

TLSA / DANE#

No TLSA records — DANE not configured for HTTPS (_443) or MX (_25)

DNSSEC#

184ms
CheckResult
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
Flagsresolution failed: failure

SOA#

No SOA record found

Registration#

WHOIS fetched 2026-11-11 19:53:15
FieldValue
RegistrarPunktum dk A/S (direct)
Registered2018-08-20
Expires2027-08-31 (282d)

Same registrant#

0 domains

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).

No other domain with this registrant in our WHOIS data yet
📋 WHOIS#

Lookup Timing#

NS
91ms
A
98ms
MX
86ms
AAAA
85ms
TXT
442ms
CAA
91ms
HTTPS
99ms
TLSA
112ms
SOA
26ms
MTA-STS
111ms
DNSSEC
184ms
SRV
98ms
Total
1217ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-10-25 02:23:26 shown 1217ms 4 NS 0 A 0 MX Bogus
2026-08-27 12:57:49 1666ms 4 NS 0 A 0 MX Bogus
2026-08-27 03:43:47 10117ms 4 NS 0 A 0 MX Bogus
2026-08-23 04:43:10 9771ms 4 NS 0 A 0 MX Bogus
2026-08-22 04:34:48 1782ms 4 NS 0 A 0 MX Bogus
2026-08-21 04:28:13 1605ms 4 NS 0 A 0 MX Bogus
2026-08-20 02:41:50 11406ms 4 NS 0 A 0 MX Bogus
2026-08-19 02:02:04 9087ms 4 NS 0 A 0 MX Bogus
2026-08-17 22:56:29 3169ms 4 NS 0 A 0 MX Bogus
2026-08-16 22:09:42 5271ms 4 NS 0 A 0 MX Bogus
2026-08-15 15:50:43 4932ms 4 NS 0 A 0 MX Bogus
2026-08-14 14:35:05 10496ms 4 NS 0 A 0 MX Bogus
2026-08-13 10:55:24 4056ms 4 NS 0 A 0 MX Bogus
2026-08-10 18:21:23 3215ms 4 NS 0 A 0 MX Bogus
2026-08-08 05:41:31 9768ms 4 NS 0 A 0 MX Bogus
2026-08-06 12:44:03 3833ms 4 NS 0 A 0 MX Bogus
2026-08-04 00:08:54 1303ms 4 NS 0 A 0 MX Bogus
2026-08-02 13:40:56 3803ms 4 NS 0 A 0 MX Bogus
2026-07-28 22:48:15 10419ms 4 NS 0 A 0 MX Bogus
2026-07-27 17:15:09 1368ms 4 NS 0 A 0 MX Bogus
2026-07-26 16:38:02 10321ms 4 NS 0 A 0 MX Bogus
2026-07-25 16:00:50 1348ms 4 NS 0 A 0 MX Bogus
2026-07-24 15:43:33 1773ms 4 NS 0 A 0 MX Bogus
2026-07-23 13:44:48 1615ms 4 NS 0 A 0 MX Bogus
2026-07-22 04:53:25 9737ms 4 NS 0 A 0 MX Bogus