trianglefolklorefestival.dk

Historical scan 2026-08-15 07:53:47  ·  ← Latest scan
Deactivated by the registry Zone File Timeline & History Scan Now

trianglefolklorefestival.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 8 August 2022 (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   52ms
NameserverIP addressesPTRASN / 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-11-19 04:02:41
www CNAMEtrianglefolklorefestival.dk (all on trianglefolklorefestival.dk)
www vs bare domainSame network
trianglefolklorefestival.dk: 46.183.138.100 (AS47292)
www.trianglefolklorefestival.dk: 46.183.138.100 (AS47292)
WildcardYes: any name under the zone resolves

TLSA / DANE#

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

DNSSEC#

2075ms
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-02 00:49:34
FieldValue
RegistrarGIGAHOST ApS
Registered2022-08-08
Expires2027-08-07 (260d)

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
52ms
A
58ms
MX
42ms
AAAA
52ms
TXT
484ms
CAA
38ms
HTTPS
43ms
TLSA
40ms
SOA
51ms
MTA-STS
61ms
DNSSEC
2075ms
SRV
153ms
Total
2700ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-19 04:02:41 687ms 5 NS 1 A 3 MX Insecure
2026-11-12 13:49:52 814ms 5 NS 1 A 3 MX Insecure
2026-11-06 01:05:04 1758ms 5 NS 1 A 3 MX Insecure
2026-11-02 00:37:41 798ms 5 NS 1 A 3 MX Insecure
2026-10-23 17:01:31 783ms 5 NS 1 A 3 MX Insecure
2026-10-15 02:28:02 1613ms 5 NS 1 A 3 MX Insecure
2026-10-08 15:53:21 2401ms 5 NS 1 A 3 MX Insecure
2026-10-01 13:05:20 1879ms 5 NS 1 A 3 MX Insecure
2026-09-30 13:02:40 778ms 5 NS 1 A 3 MX Insecure
2026-09-27 09:00:32 840ms 5 NS 1 A 3 MX Insecure
2026-09-24 11:41:13 795ms 5 NS 1 A 3 MX Insecure
2026-09-17 18:40:35 991ms 5 NS 1 A 3 MX Insecure
2026-09-11 07:30:36 985ms 5 NS 1 A 3 MX Insecure
2026-09-03 13:44:06 976ms 5 NS 1 A 3 MX Insecure
2026-09-01 23:23:03 999ms 5 NS 1 A 3 MX Insecure
2026-08-27 15:53:20 769ms 5 NS 1 A 3 MX Insecure
2026-08-21 03:40:28 9889ms 5 NS 1 A 3 MX Insecure
2026-08-19 01:07:10 14076ms 5 NS 1 A 3 MX Insecure
2026-08-17 20:05:34 707ms 1 NS 0 A 0 MX Unknown
2026-08-16 19:07:10 1286ms 1 NS 0 A 0 MX Unknown
2026-08-15 07:53:47 shown 2700ms 1 NS 0 A 0 MX Unknown
2026-08-13 17:01:50 1276ms 1 NS 0 A 0 MX Unknown
2026-08-06 18:29:26 1181ms 5 NS 1 A 3 MX Insecure
2026-08-01 21:38:09 1194ms 5 NS 1 A 3 MX Insecure
2026-07-24 01:37:50 5097ms 5 NS 0 A 3 MX Insecure