beritmillnerglas.dk

📜 Historical scan 2026-08-14 10:22:49 · ← Latest scan

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

beritmillnerglas.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 8 March 2012 (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 4197ms

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#

10306ms

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-14 23:45:06

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2012-03-08
Expires	2027-03-31 (161d)

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

4197ms

4291ms

4281ms

AAAA

4119ms

TXT

16693ms

CAA

4250ms

HTTPS

4293ms

TLSA

4091ms

SOA

4274ms

MTA-STS

4333ms

DNSSEC

10306ms

SRV

4297ms

Total

60527ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-01 01:18:29	65011ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-30 03:55:52	64999ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-26 09:36:32	59291ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 19:59:05	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 18:51:41	60534ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 18:37:57	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 18:30:24	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 10:53:59	57651ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 10:49:15	63353ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 02:03:29	59467ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 10:22:49 shown	60527ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 01:43:06	60865ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 19:54:55	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 19:13:09	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 07:29:21	59240ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 06:42:38	61262ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-04 13:33:06	61447ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 18:45:37	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 18:08:45	55627ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 17:55:31	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 17:31:45	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 17:05:38	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 16:44:17	59239ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 13:48:14	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 10:25:53	65535ms	2 NS 0 A 0 MX	❓ Unknown