faerch-koeleteknik.dk

Records from scan: 2026-08-23 07:19:51 · 6516ms total · last checked 2026-10-20 01:13 (unchanged)

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

faerch-koeleteknik.dk is a registered .dk domain whose nameservers (ns1.nordicweb.com, ns2.nordicweb.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 24 November 2010 (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#

2 records 860ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.nordicweb.com	2001:8d8:fe:53:217:160:80:161 217.160.80.161	ns-ix2.ui-dns.de ns-ix2.ui-dns.de	AS8560 IONOS SE AS8560 IONOS SE
ns2.nordicweb.com	2001:8d8:fe:53:217:160:81:161 217.160.81.161	ns-ix2.ui-dns.biz ns-ix2.ui-dns.biz	AS8560 IONOS SE AS8560 IONOS SE

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

1046ms

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: failure

🏷️ SOA#

✗ No SOA record found

📋 Registration#

WHOIS fetched 2026-10-11 16:54:19

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2010-11-24
Expires	2026-11-30 (40d)

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

860ms

740ms

692ms

AAAA

813ms

TXT

2410ms

CAA

1088ms

HTTPS

1078ms

TLSA

379ms

SOA

618ms

MTA-STS

981ms

DNSSEC

1046ms

SRV

1042ms

Total

6516ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-08-23 07:19:51 shown	6516ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 07:06:26	9812ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 06:49:06	5844ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 05:35:28	4109ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 05:11:56	3649ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 03:55:02	3275ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 18:59:03	3988ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 06:46:16	2973ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 05:41:47	3389ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 02:50:03	4599ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 06:51:06	4748ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 10:12:35	2928ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 21:29:06	1527ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 21:18:19	9267ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 20:21:49	1740ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 20:05:59	11117ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 13:50:05	11333ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 11:20:51	1779ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 02:42:22	1791ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 08:22:39	3231ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 04:53:45	5235ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-16 10:29:23	1656ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-15 09:19:33	1731ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-14 07:49:51	11212ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-13 04:55:40	9269ms	2 NS 0 A 0 MX	❓ Unknown