igr.dk

📜 Historical scan 2026-07-31 06:57:58 · ← Latest scan

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

igr.dk is a registered .dk domain whose nameservers (ns1.ipage.com, ns2.ipage.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 31 January 1997 (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 525ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.ipage.com	66.96.142.116 66.96.142.162 66.96.142.163	116.142.96.66.static.eigbox.net ns1.ipage.com ns1.ipage.com	AS29873 Newfold Digital, Inc. AS29873 Newfold Digital, Inc. AS29873 Newfold Digital, Inc.
ns2.ipage.com	65.254.254.151	65-254-254-151.yourhostingaccount.com	AS29873 Newfold Digital, 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#

601ms

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-13 00:09:10

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	1997-01-31
Expires	2027-03-31 (164d)

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

525ms

AAAA

503ms

TXT

2909ms

CAA

537ms

HTTPS

510ms

TLSA

729ms

SOA

30ms

MTA-STS

782ms

DNSSEC

601ms

SRV

2183ms

Total

6738ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-24 04:04:53	34344ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-06 23:37:54	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 00:24:57	29458ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 19:07:42	41590ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 18:51:09	35946ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 18:47:36	21310ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 16:38:11	34461ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 16:34:27	6412ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 11:15:47	36790ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 22:50:29	35323ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 23:42:10	35892ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 18:40:45	34468ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 17:31:30	6249ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 10:08:49	35852ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 20:37:32	13897ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 02:04:44	35038ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-31 06:57:58 shown	6738ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 02:32:44	36138ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 23:55:15	34562ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 23:25:27	12795ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 22:43:12	34545ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 22:22:14	35964ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 20:24:28	13321ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 17:44:04	35908ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 15:10:04	36759ms	2 NS 0 A 0 MX	❓ Unknown