fambuur.dk

📜 Historical scan 2026-09-30 19:34:22 · ← Latest scan

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

fambuur.dk is a registered .dk domain whose nameservers (ns2.123hjemmeside.dk, ns3.123hjemmeside.dk) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 9 November 2009 (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 4035ms

Nameserver	IP addresses	PTR	ASN / ISP
ns2.123hjemmeside.dk	52.200.246.146	ec2-52-200-246-146.compute-1.amazonaws.com	AS14618 Amazon.com, Inc.
ns3.123hjemmeside.dk	52.51.2.215	ec2-52-51-2-215.eu-west-1.compute.amazonaws.com	AS16509 Amazon.com, Inc.

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

10061ms

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-20 02:00:41

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2009-11-09
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#

4035ms

4031ms

4032ms

AAAA

4085ms

TXT

20176ms

CAA

4049ms

HTTPS

4033ms

TLSA

2021ms

SOA

4024ms

MTA-STS

4082ms

DNSSEC

10061ms

SRV

4082ms

Total

60492ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-09 09:52:13	63190ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-30 19:34:22 shown	60492ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-25 15:56:10	61169ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 13:43:17	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 13:20:26	62683ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 13:11:36	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 12:40:26	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 10:38:48	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 10:35:44	61387ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 04:22:55	57034ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 12:47:55	59383ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 10:22:07	62348ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 11:08:17	56283ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 22:22:51	63293ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 08:12:19	61463ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 23:20:16	57219ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-03 20:02:42	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-01 18:55:21	59222ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-31 17:56:36	57690ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-30 01:28:19	55911ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 23:00:47	61330ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 18:52:30	52125ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 18:23:51	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 18:05:19	60165ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 17:15:05	63409ms	2 NS 0 A 0 MX	❓ Unknown