kop.dk

Historical scan 2026-08-20 09:29:41  ·  ← Latest scan
Lame delegation Zone File Timeline & History Scan Now

kop.dk is a registered .dk domain whose nameservers (ns.teaminternet.dk, ns2.teaminternet.dk) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 6 October 1998 (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   16049ms

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

Web & zone#

latest probe, not this scan · checked 2026-11-17 02:42:16
www64.190.63.111 (AS47846) (address records, no CNAME)
www vs bare domainSame network
WildcardYes: any name under the zone resolves

TLSA / DANE#

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

DNSSEC#

16072ms
CheckResult
Validation Status Unknown (the delegated nameservers don't answer)
AD Flag (resolver validates) Not set
DS Record Not found
DNSKEY Record Not found
Flagsresolution failed: timed out

SOA#

No SOA record found

Registration#

WHOIS fetched 2026-11-17 03:09:45
FieldValue
RegistrarPunktum dk A/S (direct)
Registered1998-10-06
Expires2026-12-31 (44d)

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
16049ms
A
16057ms
MX
16046ms
AAAA
16040ms
TXT
65535ms
CAA
16037ms
HTTPS
16050ms
TLSA
16029ms
SOA
16048ms
MTA-STS
8051ms
DNSSEC
16072ms
SRV
16056ms
Total
65535ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-17 02:42:15 1706ms 2 NS 1 A 1 MX Insecure
2026-10-23 13:27:03 64862ms 2 NS 0 A 0 MX Unknown
2026-10-02 15:54:50 62881ms 2 NS 0 A 0 MX Unknown
2026-09-30 23:36:54 61071ms 2 NS 0 A 0 MX Unknown
2026-09-30 02:34:27 60948ms 2 NS 0 A 0 MX Unknown
2026-09-24 02:51:44 64274ms 2 NS 0 A 0 MX Unknown
2026-08-31 17:46:54 57249ms 2 NS 0 A 0 MX Unknown
2026-08-26 23:57:41 65373ms 2 NS 0 A 0 MX Unknown
2026-08-23 11:55:41 65535ms 2 NS 0 A 0 MX Unknown
2026-08-22 10:21:09 65535ms 2 NS 0 A 0 MX Unknown
2026-08-21 09:53:08 56668ms 2 NS 0 A 0 MX Unknown
2026-08-20 09:29:41 shown 65535ms 2 NS 0 A 0 MX Unknown
2026-08-19 07:19:42 65535ms 2 NS 0 A 0 MX Unknown
2026-08-15 23:26:47 56861ms 2 NS 0 A 0 MX Unknown
2026-08-14 10:23:47 65360ms 2 NS 0 A 0 MX Unknown
2026-08-13 07:06:23 61234ms 2 NS 0 A 0 MX Unknown
2026-08-11 19:22:38 61292ms 2 NS 0 A 0 MX Unknown
2026-08-10 03:38:15 57407ms 2 NS 0 A 0 MX Unknown
2026-08-07 18:53:30 61329ms 2 NS 0 A 0 MX Unknown
2026-08-06 11:17:09 61241ms 2 NS 0 A 0 MX Unknown
2026-08-03 07:38:36 65535ms 2 NS 0 A 0 MX Unknown
2026-07-31 09:38:51 59217ms 2 NS 0 A 0 MX Unknown
2026-07-29 12:49:11 61214ms 2 NS 0 A 0 MX Unknown
2026-07-28 01:24:01 59156ms 2 NS 0 A 0 MX Unknown
2026-07-27 00:58:32 63182ms 2 NS 0 A 0 MX Unknown