eventpigerne.dk

Historical scan 2026-09-24 04:04:31  ·  ← Latest scan
Zone File Timeline & History Scan Now

eventpigerne.dk is a .dk domain served by 2 nameservers (ns1.dns-parking.com, ns2.dns-parking.com). It was registered on 5 July 2024 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. The zone is not DNSSEC-signed, has no DMARC policy and is reachable over IPv6. 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   68ms

A Records#

2 records   58ms
IPTTLPTRASNISP / OrgCIDRCountryCity
217.65.156.187 60s — AS47583 — — 🇩🇪 Germany —
217.65.159.172 60s — AS47583 — — 🇩🇪 Germany —

MX Records#

No MX records found

AAAA Records (IPv6)#

2 records   51ms
IPv6 AddressTTLPTRASNISP / OrgCIDRCountryCity
2a02:4780:7f:326a:ac52:a0b:e3c9:3bcb 60s — AS47583 — — 🇨🇾 Cyprus —
2a02:4780:80:ca4f:41e3:87c5:500c:7ec6 60s — AS47583 — — 🇨🇾 Cyprus —

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-12 04:59:07

TLSA / DANE#

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

DNSSEC#

135ms
CheckResult
Validation Status Insecure
AD Flag (resolver validates) Not set
DS Record Not found
DNSKEY Record Not found
Flagsunsigned answer

SOA#

0ms
FieldValue
Serial2026092401
Primary NS (MNAME)ns1.dns-parking.com
Responsible (RNAME)dns@hostinger.com
Refresh10000s
Retry2400s
Expire604800s
Minimum (neg-cache TTL)600s

Registration#

WHOIS fetched 2026-10-30 02:26:42
FieldValue
RegistrarPunktum dk A/S (direct)
Registered2024-07-05
Expires2027-07-04 (228d)

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
68ms
A
58ms
MX
58ms
AAAA
51ms
TXT
406ms
CAA
61ms
HTTPS
58ms
TLSA
82ms
SOA
0ms
MTA-STS
86ms
DNSSEC
135ms
SRV
92ms
Total
848ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-12 04:59:07 936ms 2 NS 2 A 0 MX Insecure
2026-11-05 04:04:06 1363ms 2 NS 2 A 0 MX Insecure
2026-10-30 02:05:39 639ms 2 NS 2 A 0 MX Insecure
2026-10-28 06:10:04 725ms 2 NS 2 A 0 MX Insecure
2026-10-22 14:21:42 645ms 2 NS 2 A 0 MX Insecure
2026-10-15 22:08:59 730ms 2 NS 2 A 0 MX Insecure
2026-10-09 10:34:49 1076ms 2 NS 2 A 0 MX Insecure
2026-10-08 09:31:44 1201ms 2 NS 2 A 0 MX Insecure
2026-10-01 06:52:55 1169ms 2 NS 2 A 0 MX Insecure
2026-09-24 04:04:31 shown 848ms 2 NS 2 A 0 MX Insecure
2026-09-21 06:41:39 918ms 2 NS 2 A 0 MX Insecure
2026-09-15 10:49:38 1649ms 2 NS 2 A 0 MX Insecure
2026-09-08 08:27:48 1146ms 2 NS 2 A 0 MX Insecure
2026-08-27 22:19:10 1968ms 2 NS 2 A 0 MX Insecure
2026-08-20 11:24:00 5836ms 2 NS 2 A 0 MX Insecure
2026-08-13 10:23:30 1234ms 2 NS 2 A 0 MX Insecure
2026-08-06 17:18:27 831ms 2 NS 2 A 0 MX Insecure
2026-07-31 22:36:59 1368ms 2 NS 2 A 0 MX Insecure
2026-07-23 02:46:07 863ms 2 NS 2 A 0 MX Insecure
2026-07-17 09:55:43 821ms 2 NS 2 A 0 MX Insecure
2026-07-09 02:10:28 1046ms 2 NS 2 A 0 MX Insecure
2026-07-02 10:19:44 1800ms 2 NS 2 A 0 MX Insecure
2026-06-26 15:02:13 1035ms 2 NS 2 A 0 MX Insecure
2026-06-24 00:14:02 787ms 2 NS 2 A 0 MX Insecure
2026-06-22 22:13:23 1352ms 2 NS 2 A 0 MX Insecure