finfys.dk

📜 Historical scan 2026-07-22 17:50:37 · ← Latest scan

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

finfys.dk is a registered .dk domain whose nameservers (ns2.vpweb.com, ns3.vpweb.com, ns4.vpweb.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 25 March 2011 (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 16052ms

Nameserver	IP addresses	PTR	ASN / ISP
ns2.vpweb.com	52.4.205.198	ec2-52-4-205-198.compute-1.amazonaws.com	AS14618 Amazon.com, Inc.
ns3.vpweb.com	34.246.26.49	ec2-34-246-26-49.eu-west-1.compute.amazonaws.com	AS16509 Amazon.com, Inc.
ns4.vpweb.com	34.234.174.79	ec2-34-234-174-79.compute-1.amazonaws.com	AS14618 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#

16068ms

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-15 20:54:56

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2011-03-25
Expires	2027-03-31 (165d)

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

16052ms

16040ms

AAAA

16044ms

TXT

65535ms

CAA

16055ms

HTTPS

16046ms

TLSA

16029ms

SOA

16046ms

MTA-STS

6070ms

DNSSEC

16068ms

SRV

16050ms

Total

65535ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-08-27 18:52:37	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-23 04:54:51	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-22 04:33:12	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-21 04:24:18	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-20 03:44:16	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-19 02:18:00	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-16 19:30:04	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-15 17:56:42	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-14 03:12:35	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-12 13:51:38	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-10 16:22:13	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-07 19:47:45	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-31 00:45:14	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-27 23:22:01	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-26 22:40:22	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-25 22:22:17	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-24 22:05:04	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-23 19:18:19	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-22 17:50:37 shown	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-21 13:00:25	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-20 06:26:25	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-18 14:53:01	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-17 11:27:34	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-16 07:00:07	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-14 15:57:19	65535ms	3 NS 0 A 0 MX	❓ Unknown