hofo.dk

📜 Historical scan 2026-08-12 19:12:19 · ← Latest scan

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

hofo.dk is a registered .dk domain whose nameservers (ns1.hostinger.dk, ns2.hostinger.dk, ns3.hostinger.dk and 1 more) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 15 September 2006 (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#

4 records 1826ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.hostinger.dk	212.1.215.66	—	AS47583 Hostinger International Limited
ns2.hostinger.dk	31.220.23.1	ns2.hostinger.com	AS47583 Hostinger International Limited
ns3.hostinger.dk	145.14.150.132	—	AS47583 Hostinger International Limited
ns4.hostinger.dk	145.14.155.34	—	AS47583 Hostinger International Limited

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

1969ms

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 04:14:21

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2006-09-15
Expires	2027-09-30 (345d)

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

1826ms

1797ms

1823ms

AAAA

1799ms

TXT

8679ms

CAA

2000ms

HTTPS

1806ms

TLSA

1655ms

SOA

188ms

MTA-STS

2031ms

DNSSEC

1969ms

SRV

1853ms

Total

16943ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-08 14:25:49	14229ms	4 NS 0 A 0 MX	❓ Unknown
2026-09-30 10:56:41	14043ms	4 NS 0 A 0 MX	❓ Unknown
2026-09-29 15:43:29	14206ms	4 NS 0 A 0 MX	❓ Unknown
2026-09-06 00:55:30	15982ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-24 11:09:30	17133ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-23 10:41:07	5304ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-22 10:14:27	6361ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-21 10:02:47	18424ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-20 08:39:59	11627ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-19 06:42:40	15216ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-18 03:55:33	15141ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-17 02:51:23	18606ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-16 00:06:32	14358ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-14 16:57:38	18630ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-12 19:12:19 shown	16943ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-11 03:38:10	16846ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-09 22:48:01	17454ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-08 03:45:45	3458ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-06 18:55:53	14419ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-04 19:00:05	8619ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-27 19:24:54	11975ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-26 18:30:41	21017ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-25 17:53:08	17121ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-24 17:48:46	12336ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-23 11:44:16	4223ms	4 NS 0 A 0 MX	❓ Unknown