eye-go.dk

Historical scan 2026-08-10 09:17:51  ·  ← Latest scan
Lame delegation Zone File Timeline & History

eye-go.dk is a registered .dk domain whose nameservers (ns61.domaincontrol.com, ns62.domaincontrol.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 17 October 2017 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. We saw it become registrar-handled on 4 November 2026, when it moved from direct registration at Punktum to ONE.COM A/S. 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   599ms

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-11-09 11:44:56
www46.30.211.38 (AS51468) (address records, no CNAME)
www vs bare domainSame network
eye-go.dk: 46.30.211.38 (AS51468)
www.eye-go.dk: 46.30.211.38 (AS51468)
WildcardNo
Denial of existenceNSEC3 · 0 iterations · no salt RFC 9276 ✓
CDS / CDNSKEYNone 0 CDS, 0 CDNSKEY

TLSA / DANE#

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

DNSSEC#

883ms
CheckResult
Validation Status Unknown (the delegated nameservers don't answer)
AD Flag (resolver validates) Not set
DS Record Not found
DNSKEY Record Not found
Flagsresolution failed: failure

SOA#

No SOA record found

Registration#

WHOIS fetched 2026-11-04 11:51:12
FieldValue
RegistrarONE.COM A/S
Registered2017-10-17
Expires2027-10-31 (342d)

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#

NS
599ms
A
682ms
MX
601ms
AAAA
618ms
TXT
2727ms
CAA
680ms
HTTPS
692ms
TLSA
431ms
SOA
311ms
MTA-STS
813ms
DNSSEC
883ms
SRV
923ms
Total
5316ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-09 11:44:56 438ms 2 NS 1 A 1 MX Secure
2026-11-04 11:39:20 409ms 2 NS 1 A 1 MX Secure
2026-11-01 00:52:48 5001ms 2 NS 0 A 0 MX Unknown
2026-10-30 03:59:51 5048ms 2 NS 0 A 0 MX Unknown
2026-10-29 01:15:19 5089ms 2 NS 0 A 0 MX Unknown
2026-10-08 22:29:29 2964ms 2 NS 0 A 0 MX Unknown
2026-08-23 22:41:36 21835ms 2 NS 0 A 0 MX Unknown
2026-08-22 21:05:12 2971ms 2 NS 0 A 0 MX Unknown
2026-08-21 20:49:43 7946ms 2 NS 0 A 0 MX Unknown
2026-08-20 20:45:13 11239ms 2 NS 0 A 0 MX Unknown
2026-08-19 18:25:21 6589ms 2 NS 0 A 0 MX Unknown
2026-08-18 18:23:23 5446ms 2 NS 0 A 0 MX Unknown
2026-08-17 05:07:06 4946ms 2 NS 0 A 0 MX Unknown
2026-08-15 18:41:15 2988ms 2 NS 0 A 0 MX Unknown
2026-08-14 16:13:59 2949ms 2 NS 0 A 0 MX Unknown
2026-08-12 22:11:59 4369ms 2 NS 0 A 0 MX Unknown
2026-08-11 18:19:45 4256ms 2 NS 0 A 0 MX Unknown
2026-08-10 09:17:51 shown 5316ms 2 NS 0 A 0 MX Unknown
2026-08-07 18:53:05 4241ms 2 NS 0 A 0 MX Unknown
2026-07-29 23:11:46 10942ms 2 NS 0 A 0 MX Unknown
2026-07-28 12:01:40 3440ms 2 NS 0 A 0 MX Unknown
2026-07-27 07:07:28 2806ms 2 NS 0 A 0 MX Unknown
2026-07-26 06:53:30 11030ms 2 NS 0 A 0 MX Unknown
2026-07-25 06:33:39 11876ms 2 NS 0 A 0 MX Unknown
2026-07-24 05:11:19 9107ms 2 NS 0 A 0 MX Unknown