karinbd.dk

📜 Historical scan 2026-07-29 15:34:36 · ← Latest scan

🧟 Lame delegation ⬇ Zone File 📜 Timeline & History ⚡ Scan Now

karinbd.dk is a registered .dk domain whose nameservers (dns01.mhhosting.dk, dns02.mhhosting.dk, dns03.mhhosting.dk) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 2 January 2015 (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#

3 records 4028ms

Nameserver	IP addresses	PTR	ASN / ISP
dns01.mhhosting.dk	188.180.76.248	dns01.mhhosting.dk	AS3292 TDC Holding A/S
dns02.mhhosting.dk	188.180.76.244	dns02.mhhosting.dk	AS3292 TDC Holding A/S
dns03.mhhosting.dk	80.63.220.2	2.220.63.80.customer.static.mhhosting.dk	AS3292 TDC Holding A/S

🌍 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#

10062ms

Check	Result
Validation Status	❓ Unknown (the delegated nameservers don't answer)
AD Flag (resolver validates)	✗ Not set
DS Record	✗ Not found
DNSKEY Record	✗ Not found
Flags	resolution failed: timed out

🏷️ SOA#

✗ No SOA record found

📋 Registration#

WHOIS fetched 2026-10-11 22:20:25

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2015-01-02
Expires	2027-01-31 (106d)

🔗 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#

4028ms

4029ms

4027ms

AAAA

4031ms

TXT

18202ms

CAA

4026ms

HTTPS

4028ms

TLSA

101ms

SOA

4028ms

MTA-STS

4037ms

DNSSEC

10062ms

SRV

4031ms

Total

29195ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-07 18:27:17	28971ms	3 NS 0 A 0 MX	❓ Unknown
2026-10-01 03:16:16	27208ms	3 NS 0 A 0 MX	❓ Unknown
2026-09-30 06:32:48	29036ms	3 NS 0 A 0 MX	❓ Unknown
2026-09-26 07:32:12	29838ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-27 22:58:06	32011ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-23 23:12:34	39720ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-22 15:28:10	39846ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-21 14:59:51	64551ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-20 14:36:03	32446ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-19 07:46:14	35424ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-18 04:45:22	40581ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-16 12:00:43	26729ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-14 19:00:25	29613ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-13 16:45:08	26559ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-12 15:01:05	31613ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-10 08:14:58	29474ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-09 03:26:07	27465ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-06 23:58:40	29301ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-02 04:08:11	28642ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-29 15:34:36 shown	29195ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-28 05:08:19	52951ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-27 04:35:39	35308ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-26 04:23:08	46322ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-25 03:52:04	35771ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-24 03:13:46	49614ms	3 NS 0 A 0 MX	❓ Unknown