4solutions.dk

📜 Historical scan 2026-08-06 16:39:56 · ← Latest scan

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

4solutions.dk is a registered .dk domain whose nameservers (ns.scannet2.dk, ns2.scannet2.dk) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 18 January 2002 (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 43ms

Nameserver	IP addresses	PTR	ASN / ISP
ns.scannet2.dk	185.25.141.9 2a02:2339:4006:10d::4171:4171	ns1.scannet.dk ns1.scannet.dk	AS48854 team.blue Denmark A/S AS48854 team.blue Denmark A/S
ns2.scannet2.dk	2a02:2339:1:112:0:5:1:b11 91.197.248.72	ns2.scannet.dk ns2.scannet.dk	AS48854 team.blue Denmark A/S AS48854 team.blue Denmark 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#

8370ms

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-17 10:31:48

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2002-01-18
Expires	2027-03-31 (163d)

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

43ms

319ms

8326ms

AAAA

95ms

TXT

385ms

CAA

8347ms

HTTPS

97ms

TLSA

71ms

SOA

31ms

MTA-STS

103ms

DNSSEC

8370ms

SRV

361ms

Total

9200ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-02 15:12:25	924ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-26 18:29:27	2850ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 15:40:49	1113ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 14:05:58	1112ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 13:37:42	1470ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 13:28:20	9945ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 09:58:43	7646ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 09:56:05	1062ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 12:07:42	3315ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 05:25:56	1192ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 01:46:29	9370ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 08:37:27	9351ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 00:21:47	3485ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 13:50:30	1602ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 16:39:56 shown	9200ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 21:14:01	10126ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 06:27:47	869ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 06:20:39	1054ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 05:47:29	2806ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 05:32:04	9959ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 03:28:22	985ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 00:11:26	1174ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 06:13:05	1078ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 20:50:22	9176ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-17 20:21:23	1154ms	2 NS 0 A 0 MX	❓ Unknown