avyna.dk

📜 Historical scan 2026-08-15 09:13:06 · ← Latest scan

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

avyna.dk is a registered .dk domain whose nameservers (ns.prezent.nl, ns2.prezent.nl, ns3.prezent.nl) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 2 October 2012 (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#

3 records 4249ms

Nameserver	IP addresses	PTR	ASN / ISP
ns.prezent.nl	2a01:7c8:aab2:ce:5054:ff:fe66:ffdd	—	AS20857 Signet B.V.
ns2.prezent.nl	2a05:d014:953:a00:29d9:cb1d:781:5b5c	—	AS16509 Amazon.com, Inc.
ns3.prezent.nl	2600:1f14:174:8600:6174:d59d:30a8:5f34 34.217.216.158	— ec2-34-217-216-158.us-west-2.compute.amazonaws.com	AS16509 Amazon.com, Inc. AS16509 Amazon.com, 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#

10443ms

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: timed out

🏷️ SOA#

✗ No SOA record found

📋 Registration#

WHOIS fetched 2026-10-25 15:04:01

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2012-10-02
Expires	2026-10-31 (5d)

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

4249ms

4246ms

4218ms

AAAA

4207ms

TXT

14488ms

CAA

4229ms

HTTPS

4230ms

TLSA

2056ms

SOA

4229ms

MTA-STS

4295ms

DNSSEC

10443ms

SRV

4248ms

Total

49624ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-30 20:47:11	45561ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-24 10:12:24	48844ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-23 08:22:15	49807ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-22 07:55:52	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-21 07:33:39	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-20 07:09:30	51136ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-19 03:12:43	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-18 00:50:34	48595ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-16 17:42:33	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-15 09:13:06 shown	49624ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-13 16:24:12	50226ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-12 12:13:50	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-10 11:46:47	48647ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-07 02:03:24	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-03 05:32:01	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-01 17:45:16	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-29 20:43:25	51058ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-27 12:30:06	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-26 11:45:52	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-25 11:17:41	47001ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-24 11:07:47	21231ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-23 09:27:19	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-22 06:26:54	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-20 18:40:17	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-19 12:47:25	65535ms	3 NS 0 A 0 MX	❓ Unknown