3f-frb.dk

📜 Historical scan 2026-08-16 08:36:54 · ← Latest scan

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

3f-frb.dk is a registered .dk domain whose nameservers (ns01.one.com, ns02.one.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 8 December 2015 (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 437ms

Nameserver	IP addresses	PTR	ASN / ISP
ns01.one.com	195.206.121.10 2001:67c:28cc::10	ns01.one.com ns01.one.com	AS197495 One.com A/S AS197495 One.com A/S
ns02.one.com	185.10.11.10 2001:67c:3c0::10	ns02.one.com ns02.one.com	AS51468 One.com A/S AS51468 One.com 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#

683ms

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-21 15:54:50

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2015-12-08
Expires	2026-12-31 (69d)

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

437ms

457ms

442ms

AAAA

467ms

TXT

1292ms

CAA

450ms

HTTPS

438ms

TLSA

318ms

SOA

331ms

MTA-STS

495ms

DNSSEC

683ms

SRV

553ms

Total

4824ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-27 02:45:33	1262ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-01 03:04:12	2947ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-28 09:49:09	3565ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 08:18:05	3067ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 06:02:09	5990ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 05:29:13	10201ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 05:14:01	2994ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 04:54:32	4990ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 03:53:54	2252ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 12:51:17	1441ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 08:36:54 shown	4824ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 05:44:59	3750ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 21:09:02	2760ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 09:52:07	1498ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 05:34:58	3054ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 02:50:21	989ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-31 14:48:48	1452ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 07:29:47	1415ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 00:38:17	25048ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 23:28:36	8816ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 22:38:45	1069ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 22:32:24	16806ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 18:17:58	10125ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 16:38:41	9015ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 14:50:32	17080ms	2 NS 0 A 0 MX	❓ Unknown