emolife.dk

📜 Historical scan 2026-08-13 22:54:53 · ← Latest scan

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

emolife.dk is a registered .dk domain whose nameservers (ns1.ns-serve.net, ns2.ns-serve.net) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 19 January 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 514ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.ns-serve.net	195.191.92.140 2001:67c:2394:2::1001	ns1.ns-serve.net ns1.ns-serve.net	AS57115 Vautron Rechenzentrum AG AS25504 Vautron Rechenzentrum AG
ns2.ns-serve.net	195.191.93.140 2001:67c:2394:4::1001	ns2.ns-serve.net ns2.ns-serve.net	AS57115 Vautron Rechenzentrum AG AS25504 Vautron Rechenzentrum AG

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

505ms

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-19 17:54:38

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2011-01-19
Expires	2027-01-31 (103d)

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

514ms

517ms

520ms

AAAA

509ms

TXT

2229ms

CAA

455ms

HTTPS

462ms

TLSA

449ms

SOA

39ms

MTA-STS

525ms

DNSSEC

505ms

SRV

520ms

Total

4078ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-08-28 06:00:24	6859ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 17:59:27	2039ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 17:33:43	8003ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 17:29:26	11960ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 17:23:42	6943ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 17:09:24	11810ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 17:08:58	7014ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 15:40:48	4038ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 13:07:12	2033ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 22:54:53 shown	4078ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 19:45:09	7724ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 19:42:21	2529ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 07:56:29	5752ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 19:32:11	4754ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 19:17:34	4121ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 18:54:19	1976ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 18:31:08	4734ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 17:01:48	11911ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 08:11:01	2298ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 02:08:36	4167ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 23:37:34	12116ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 23:02:28	2061ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-17 20:48:23	4677ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-15 23:15:03	2199ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-13 14:47:33	4875ms	2 NS 0 A 0 MX	❓ Unknown