yobber.dk

📜 Historical scan 2026-07-27 19:28:48 · ← Latest scan

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

yobber.dk is a registered .dk domain whose nameservers (ns1.wk.se, ns2.wk.se) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 25 November 2025 (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 93ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.wk.se	193.0.253.8 2001:67c:2b58:1::100	ns1.wk.se ns1.wk.se	AS41980 Webbkonsulterna i Jamtland AB AS41980 Webbkonsulterna i Jamtland AB
ns2.wk.se	2a02:752:0:18::1aa8 46.246.45.249	ns2.wk.se ns2.wk.se	AS42708 Glesys AB AS42708 Glesys AB

🌍 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-18 16:32:06

Field	Value
Registrar	1API GmbH
Registered	2025-11-25
Expires	2026-11-24 (36d)

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

93ms

117ms

127ms

AAAA

110ms

TXT

512ms

CAA

104ms

HTTPS

112ms

TLSA

90ms

SOA

40ms

MTA-STS

223ms

DNSSEC

197ms

SRV

272ms

Total

1464ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-01 04:20:26	2947ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-25 18:59:18	10995ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 17:55:37	11051ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 12:45:54	9261ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 12:34:24	4727ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 12:04:11	6888ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 04:14:55	1567ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 02:14:31	1404ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 06:36:45	11087ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 02:30:57	6196ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 08:57:09	4415ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 14:07:13	11050ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 23:33:40	9139ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 14:30:01	11162ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-02 22:43:21	11086ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 19:28:48 shown	1464ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 19:07:07	1647ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 18:50:48	1880ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 18:36:12	9079ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 17:42:09	2053ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 15:40:41	1275ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 11:52:52	1886ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 07:10:10	1716ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 06:23:09	10931ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 05:16:04	5701ms	2 NS 0 A 0 MX	❓ Unknown