beringerne.dk

📜 Historical scan 2026-07-27 04:36:51 · ← Latest scan

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

beringerne.dk is a registered .dk domain whose nameservers (cpanel-ns1.cloudns.dk, cpanel-ns2.cloudns.dk, cpanel-ns3.cloudns.dk) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 26 October 2004 (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 32ms

Nameserver	IP addresses	PTR	ASN / ISP
cpanel-ns1.cloudns.dk	104.236.38.47	ns1.serverhostgroup.com	AS14061 DigitalOcean, LLC
cpanel-ns2.cloudns.dk	46.101.214.99	ns2.serverhostgroup.com	AS14061 DigitalOcean, LLC
cpanel-ns3.cloudns.dk	93.113.174.242	orion.hosterion.net	AS43927 Hosterion Srl

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

270ms

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-16 01:21:35

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2004-10-26
Expires	2027-10-31 (379d)

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

32ms

197ms

220ms

AAAA

208ms

TXT

1788ms

CAA

216ms

HTTPS

199ms

TLSA

327ms

SOA

21ms

MTA-STS

182ms

DNSSEC

270ms

SRV

8270ms

Total

9935ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-23 12:30:29	12054ms	3 NS 0 A 0 MX	❓ Unknown
2026-09-04 00:51:44	11065ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-24 12:15:10	16115ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-23 06:26:09	3719ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-22 06:11:03	12479ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-21 05:54:07	11069ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-20 05:38:03	11610ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-19 03:56:56	6344ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-17 18:36:06	17392ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-16 17:51:06	28794ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-15 23:16:50	13662ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-14 21:22:30	13386ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-12 13:21:18	15984ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-11 12:03:10	15660ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-10 05:44:45	12090ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-09 02:39:34	12740ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-06 10:35:01	11024ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-02 06:07:02	11290ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-28 04:51:06	15526ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-27 04:36:51 shown	9935ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-26 04:08:47	19987ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-25 03:51:40	2997ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-24 02:23:15	15502ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-23 02:03:06	11311ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-21 22:14:42	15363ms	3 NS 0 A 0 MX	❓ Unknown