jger.dk

📜 Historical scan 2026-10-02 02:44:50 · ← Latest scan

🚫 Deactivated by the registry ⬇ Zone File 📜 Timeline & History ⚡ Scan Now

jger.dk is a .dk domain the registry has taken out of service: it is delegated to the registry's own sentinel nameservers (nonexistent.punktum.dk), so it does not resolve. It was registered on 9 September 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#

1 records 47ms

Nameserver	IP addresses	PTR	ASN / ISP
nonexistent.punktum.dk	—	—	—

🌍 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

🧩 Web & zone#

latest probe, not this scan · checked 2026-10-16 16:58:10

www CNAME	jger.dk (all on jger.dk) → 46.183.139.205 (AS47292)
www vs bare domain	Same network jger.dk: 46.183.139.205 (AS47292) www.jger.dk: 46.183.139.205 (AS47292)
Wildcard	Yes: any name under the zone resolves

🔗 TLSA / DANE#

✗ No TLSA records — DANE not configured for HTTPS (_443) or MX (_25)

🔐 DNSSEC#

118ms

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 17:38:03

Field	Value
Registrar	GIGAHOST ApS
Registered	2004-09-09
Expires	2027-09-30 (346d)

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

47ms

35ms

41ms

AAAA

47ms

TXT

117ms

CAA

31ms

HTTPS

33ms

TLSA

22ms

SOA

44ms

MTA-STS

49ms

DNSSEC

118ms

SRV

53ms

Total

874ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-16 16:58:10	969ms	5 NS 1 A 3 MX	🔓 Insecure
2026-10-15 16:20:24	100ms	1 NS 0 A 0 MX	❓ Unknown
2026-10-14 11:38:31	114ms	1 NS 0 A 0 MX	❓ Unknown
2026-10-13 11:08:43	222ms	1 NS 0 A 0 MX	❓ Unknown
2026-10-12 06:51:17	102ms	1 NS 0 A 0 MX	❓ Unknown
2026-10-11 05:10:33	218ms	1 NS 0 A 0 MX	❓ Unknown
2026-10-10 04:04:32	102ms	1 NS 0 A 0 MX	❓ Unknown
2026-10-08 11:23:34	256ms	1 NS 0 A 0 MX	❓ Unknown
2026-10-07 11:15:50	138ms	1 NS 0 A 0 MX	❓ Unknown
2026-10-06 03:16:20	237ms	1 NS 0 A 0 MX	❓ Unknown
2026-10-05 03:12:59	518ms	1 NS 0 A 0 MX	❓ Unknown
2026-10-04 02:51:23	157ms	1 NS 0 A 0 MX	❓ Unknown
2026-10-03 02:49:49	110ms	1 NS 0 A 0 MX	❓ Unknown
2026-10-02 02:44:50 shown	874ms	1 NS 0 A 0 MX	❓ Unknown
2026-10-01 02:37:49	1622ms	5 NS 1 A 3 MX	🔓 Insecure
2026-09-25 01:06:31	1009ms	5 NS 1 A 3 MX	🔓 Insecure
2026-09-21 22:53:39	750ms	5 NS 1 A 3 MX	🔓 Insecure
2026-09-14 21:41:31	867ms	5 NS 1 A 3 MX	🔓 Insecure
2026-09-08 05:25:12	710ms	5 NS 1 A 3 MX	🔓 Insecure
2026-08-27 08:19:18	762ms	5 NS 1 A 3 MX	🔓 Insecure
2026-08-20 18:59:47	7296ms	5 NS 1 A 3 MX	🔓 Insecure
2026-08-13 17:12:35	9242ms	5 NS 1 A 3 MX	🔓 Insecure
2026-08-10 01:51:03	1361ms	5 NS 1 A 3 MX	🔓 Insecure
2026-08-02 04:20:24	1534ms	5 NS 1 A 3 MX	🔓 Insecure
2026-07-23 23:47:16	2770ms	5 NS 1 A 3 MX	🔓 Insecure