yume-cph.dk

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

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

yume-cph.dk is a registered .dk domain whose nameservers (ns01.one.com, ns02.one.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 16 January 2017 (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 88ms

Nameserver	IP addresses	PTR	ASN / ISP
ns01.one.com	195.206.121.10 2001:67c:28cc::10	ns01.one.com ns01.one.com	AS197495 One.com A/S AS197495 One.com A/S
ns02.one.com	185.10.11.10 2001:67c:3c0::10	ns02.one.com ns02.one.com	AS51468 One.com A/S AS51468 One.com A/S

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

197ms

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-06 04:42:23

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2017-01-16
Expires	2027-01-31 (101d)

📋 WHOIS#

⏱️ Lookup Timing#

88ms

91ms

115ms

AAAA

84ms

TXT

426ms

CAA

108ms

HTTPS

79ms

TLSA

82ms

SOA

69ms

MTA-STS

102ms

DNSSEC

197ms

SRV

290ms

Total

1052ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-26 04:45:02	1641ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-27 14:19:19	1660ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 21:06:15	10190ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 17:48:19	4081ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 17:43:04	4541ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 17:35:33	5334ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 13:42:06	27366ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 13:38:37	2699ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 01:04:11	10238ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 06:08:13	8821ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 01:40:33	2644ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 19:57:32	2824ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 13:02:49	3763ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 21:18:56	10077ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-05 22:47:29	1428ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-02 16:34:50	31211ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 13:36:44	2241ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 05:26:39	1082ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 04:47:04 shown	1052ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 04:12:07	1036ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 03:43:52	16878ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 03:24:12	992ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 23:30:52	1072ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 10:16:25	23236ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 21:05:01	1022ms	2 NS 0 A 0 MX	❓ Unknown