fygi.dk

📜 Historical scan 2026-08-03 09:11:30 · ← Latest scan

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

fygi.dk is a registered .dk domain whose nameservers (ns1.jth.net, ns4.jth.net) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 30 September 2004 (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#

2 records 962ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.jth.net	212.237.178.27 2a06:4005:8003::2	ns1.jth.net vennely.jth.net	AS204151 EWII Bredbaand A/S AS204151 EWII Bredbaand A/S
ns4.jth.net	2a06:4004:b026::1 87.104.241.106	— ns4.jth.net	AS204151 EWII Bredbaand A/S AS204151 EWII Bredbaand A/S

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

1613ms

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: failure

🏷️ SOA#

✗ No SOA record found

📋 Registration#

WHOIS fetched 2026-10-12 19:27:14

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2004-09-30
Expires	2027-09-30 (347d)

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

962ms

784ms

1895ms

AAAA

1908ms

TXT

6176ms

CAA

856ms

HTTPS

996ms

TLSA

2229ms

SOA

52ms

MTA-STS

2823ms

DNSSEC

1613ms

SRV

2994ms

Total

10196ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-30 11:27:17	32334ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-30 00:44:29	25298ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 12:00:52	45202ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 10:19:59	3402ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 09:53:16	23465ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 09:02:12	31686ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 05:50:06	46244ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 06:12:36	35830ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 02:44:13	32667ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 10:32:48	34383ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 07:22:21	34195ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 06:57:40	9024ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-03 09:11:30 shown	10196ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 07:59:29	2658ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 07:42:33	2712ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 07:29:08	18675ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 07:13:14	2962ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 06:13:11	29393ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 02:34:27	31551ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 12:27:39	2648ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 11:39:32	25566ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 06:36:29	4293ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-16 21:26:22	9688ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-15 04:09:17	11648ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-13 21:18:14	9697ms	2 NS 0 A 0 MX	❓ Unknown