4fairlife.dk

📜 Historical scan 2026-08-03 17:43:43 · ← Latest scan

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

4fairlife.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 7 August 2014 (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 76ms

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#

139ms

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-20 12:54:16

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2014-08-07
Expires	2027-08-31 (312d)

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

76ms

70ms

AAAA

71ms

TXT

319ms

CAA

75ms

HTTPS

87ms

TLSA

56ms

SOA

20ms

MTA-STS

61ms

DNSSEC

139ms

SRV

131ms

Total

843ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-07 18:28:15	1228ms	2 NS 0 A 0 MX	❓ Unknown
2026-10-04 05:41:50	1242ms	2 NS 0 A 0 MX	❓ Unknown
2026-10-01 03:49:54	1197ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-03 22:55:20	1310ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 04:20:21	6214ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 04:12:17	8798ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 04:05:11	9097ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 02:54:20	4473ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 00:24:29	2882ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 09:07:22	2877ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 21:14:54	10063ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 17:23:03	880ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 04:00:24	3593ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 00:28:42	977ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 12:31:01	10213ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 16:51:03	1584ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-03 17:43:43 shown	843ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-02 03:21:34	40209ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 06:28:27	900ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 06:18:57	954ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 05:46:43	949ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 04:55:40	10033ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 03:54:12	49508ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 01:16:49	871ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 23:36:29	16966ms	2 NS 0 A 0 MX	❓ Unknown