managed-security.dk

📜 Historical scan 2026-06-17 22:28:32 · ← Latest scan

⬇ Zone File 📜 Timeline & History ⚡ Scan Now

managed-security.dk is a .dk domain served by 2 nameservers (ns01.dubex.net, ns02.dubex.net). It was already in the .dk zone when our tracking began on 16 June 2026. The zone is not DNSSEC-signed, publishes a DMARC policy and has no IPv6 address. 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 133ms

Nameserver	IP addresses	PTR	ASN / ISP
ns01.dubex.net	185.171.197.77	ns01.dubex.net	AS3292 TDC Holding A/S
ns02.dubex.net	185.171.197.78	ns02.dubex.net	AS3292 TDC Holding 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#

1 records 271ms

TXT Record
v=spf1 include:dubex.dk -all

✉️ SPF#

Policy	Record (managed-security.dk)
-all (hard fail)	v=spf1 include:dubex.dk -all

📨 DMARC#

Policy	Record (_dmarc.managed-security.dk)
p=reject	v=DMARC1;p=reject;adkim=s;aspf=s;rua=mailto:dmarc-rua@dubex.dk;ruf=mailto:dmarc-ruf@dubex.dk;rf=afrf;pct=100;ri=86400;fo=1

📬 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

🔎 SPF check#

zone-wide SPF report

DNS lookups: 6/10 · policy: -all

No problems found

🔗 TLSA / DANE#

✗ No TLSA records — DANE not configured for HTTPS (_443) or MX (_25)

🔐 DNSSEC#

199ms

Check	Result
Validation Status	🔓 Insecure
AD Flag (resolver validates)	✗ Not set
DS Record	✗ Not found
DNSKEY Record	✗ Not found
Flags	resolution failed: ncache nxrrset

🏷️ SOA#

127ms

Field	Value
Serial	5
Primary NS (MNAME)	ib.dubex.net
Responsible (RNAME)	hostmaster@dubex.dk
Refresh	10800s
Retry	3600s
Expire	2419200s
Minimum (neg-cache TTL)	900s

📋 Registration#

✗ No registration data yet — queued for a WHOIS lookup

📋 WHOIS#

⏱️ Lookup Timing#

133ms

145ms

AAAA

130ms

TXT

271ms

CAA

133ms

HTTPS

132ms

TLSA

122ms

SOA

127ms

MTA-STS

131ms

DNSSEC

199ms

SRV

162ms

Total

857ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-02 17:26:41	65008ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-26 20:52:58	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-28 10:38:40	63889ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 09:49:43	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 07:33:45	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 07:12:37	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 07:01:40	61314ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 06:00:35	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 05:21:58	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 20:03:44	59932ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 02:55:58	61416ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 14:17:07	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 03:43:38	60838ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 21:53:36	59364ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 10:55:15	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 10:17:13	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 07:59:06	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 07:48:09	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 07:22:15	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 06:53:02	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 05:38:18	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 22:23:53	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 21:20:54	61304ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 14:07:28	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 10:07:41	64766ms	2 NS 0 A 0 MX	❓ Unknown