savran.dk

📜 Historical scan 2026-08-01 12:02:35 · ← Latest scan

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

savran.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 29 April 2019 (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 16035ms

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#

16064ms

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-11 12:20:19

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2019-04-29
Expires	2027-04-30 (191d)

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

16035ms

16037ms

AAAA

16045ms

TXT

12675ms

CAA

8273ms

HTTPS

8044ms

TLSA

510ms

SOA

32ms

MTA-STS

8445ms

DNSSEC

16064ms

SRV

16052ms

Total

19837ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-29 18:01:49	13672ms	4 NS 0 A 0 MX	❓ Unknown
2026-09-25 06:20:07	16180ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-26 00:10:00	16182ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-23 15:37:51	16541ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-22 11:50:19	19861ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-21 11:21:58	6042ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-20 10:15:36	4866ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-19 07:27:34	7938ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-18 07:04:19	3954ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-17 04:12:44	17360ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-15 08:22:20	11472ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-14 02:07:32	18853ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-11 20:56:24	15191ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-10 19:46:35	18030ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-08 20:36:51	16378ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-06 13:09:39	14137ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-02 12:55:48	15156ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-01 12:02:35 shown	19837ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-27 23:35:11	12279ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-26 22:05:31	4137ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-25 21:39:09	17750ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-24 21:02:39	29420ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-23 19:42:32	14150ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-22 18:59:46	5604ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-21 17:35:22	16523ms	4 NS 0 A 0 MX	❓ Unknown