dbifyn.dk

📜 Historical scan 2026-07-20 11:00:14 · ← Latest scan

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

dbifyn.dk is a registered .dk domain whose nameservers (ns4.123hjemmeside.dk, ns5.123hjemmeside.dk) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 18 July 2011 (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 58ms

Nameserver	IP addresses	PTR	ASN / ISP
ns4.123hjemmeside.dk	52.51.2.215	ec2-52-51-2-215.eu-west-1.compute.amazonaws.com	AS16509 Amazon.com, Inc.
ns5.123hjemmeside.dk	52.200.246.146	ec2-52-200-246-146.compute-1.amazonaws.com	AS14618 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#

16068ms

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-12 22:07:34

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2011-07-18
Expires	2027-07-31 (287d)

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

58ms

16051ms

45ms

AAAA

11052ms

TXT

12200ms

CAA

8057ms

HTTPS

42ms

TLSA

2082ms

SOA

8056ms

MTA-STS

16044ms

DNSSEC

16068ms

SRV

16051ms

Total

64894ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-28 08:53:15	63511ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-01 10:21:45	63403ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-27 06:50:04	64038ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 22:53:54	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 22:26:49	63149ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 22:18:19	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 20:37:57	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 20:30:37	61540ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 17:50:56	61881ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 19:11:34	59255ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 04:59:27	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 04:23:33	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 18:03:37	61483ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 14:58:54	59329ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-02 04:49:04	61365ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 13:41:52	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 21:27:36	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 21:16:25	59247ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 20:57:44	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 20:21:36	56797ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 18:54:30	63257ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 15:07:40	61210ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 11:56:00	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 11:00:14 shown	64894ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 01:51:38	65535ms	2 NS 0 A 0 MX	❓ Unknown