boys2men.dk

📜 Historical scan 2026-08-21 11:31:42 · ← Latest scan

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

boys2men.dk is a registered .dk domain whose nameservers (ns1.simply.com, ns2.simply.com, ns3.simply.com) do not answer for it, so it is currently a lame delegation and does not resolve. It 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#

3 records 549ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.simply.com	2a02:2339:1:15c::4562:4562 91.197.248.78	ns1.simply.com ns1.simply.com	AS48854 team.blue Denmark A/S AS48854 team.blue Denmark A/S
ns2.simply.com	185.25.141.15 2a02:2339:4006:101::4562:4562	ns2.simply.com ns2.simply.com	AS48854 team.blue Denmark A/S AS48854 team.blue Denmark A/S
ns3.simply.com	91.197.248.79	ns3.simply.com	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#

1042ms

Check	Result
Validation Status	⚠️ Bogus — the parent still publishes a DS record, but the delegated nameservers don't answer, so no signed answer can be fetched. The zone isn't serving broken signatures; it isn't serving at all.
AD Flag (resolver validates)	✗ Not set
DS Record	✓ Found
DNSKEY Record	✗ Not found
Flags	resolution failed: failure

🏷️ SOA#

✗ No SOA record found

📋 Registration#

✗ No registration data yet — queued for a WHOIS lookup

📋 WHOIS#

⏱️ Lookup Timing#

549ms

544ms

629ms

AAAA

559ms

TXT

2011ms

CAA

603ms

HTTPS

678ms

TLSA

333ms

SOA

378ms

MTA-STS

963ms

DNSSEC

1042ms

SRV

854ms

Total

6843ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-12 03:17:57	10098ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-27 05:44:37	2956ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-23 13:51:24	5204ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-22 11:36:01	7062ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-21 11:31:42 shown	6843ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-20 11:22:18	1910ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-19 09:14:29	3754ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-18 09:11:11	10139ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-16 20:04:04	9105ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-14 23:33:15	4767ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-12 04:50:11	10234ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-10 07:57:59	3550ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-08 22:00:06	10287ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-02 06:38:52	1331ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-07-30 02:24:34	10328ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-27 12:07:56	1123ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-07-26 11:41:43	10026ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-07-25 11:21:00	1557ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-07-24 06:56:10	1250ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-07-23 04:12:36	1150ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-07-22 01:04:28	1266ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-07-21 00:41:34	1160ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-07-19 20:40:29	1364ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-07-18 18:20:57	10204ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-07-17 13:19:49	10053ms	3 NS 0 A 0 MX	⚠️ Bogus