vildbjerg-cup.dk

📜 Historical scan 2026-07-02 13:31:00 · ← Latest scan

⬇ Zone File 📜 Timeline & History ⚡ Scan Now

vildbjerg-cup.dk is a .dk domain served by 2 nameservers (ns.bodata.dk, ns2.bodata.dk). It was registered on 30 August 1996 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. Its website address 37.35.100.21 is hosted by Bo data ApS (AS49974) in Denmark. Mail is handled by vildbjergcup-dk02c.mail.protection.outlook.com. The zone is not DNSSEC-signed, has no 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 419ms

Nameserver	IP addresses	PTR	ASN / ISP
ns.bodata.dk	213.5.32.131	ns.bodata.dk	AS49974 Bo data ApS
ns2.bodata.dk	213.5.32.132	ns2.bodata.dk	AS49974 Bo data ApS

🌍 A Records#

1 records 42ms

IP	TTL	PTR	ASN	ISP / Org	CIDR	Country	City
37.35.100.21	3600s	37-35-100-21.static.ip.bodata.dk	AS49974	Bo data ApS	37.35.96.0/21	🇩🇰 Denmark	—

📧 MX Records#

1 records 428ms

Priority	TTL	Mail Server	IP addresses	PTR	ASN
10	3600s	vildbjergcup-dk02c.mail.protection.outlook.com	2a01:111:f403:ca04::4 2a01:111:f403:ca04::6 2a01:111:f403:ca04::b 2a01:111:f403:ca04::e 52.101.68.36 52.101.73.1 52.101.73.19 52.101.73.4	mail-db4pr02cu00204.inbound.protection.outlook.com mail-db4pr02cu00406.inbound.protection.outlook.com mail-dbbpr03cu00103.inbound.protection.outlook.com mail-db8pr02cu00106.inbound.protection.outlook.com mail-db5pr02cu00104.inbound.protection.outlook.com mail-am3pr04cu00501.inbound.protection.outlook.com mail-as8pr04cu00803.inbound.protection.outlook.com mail-am0pr83cu00404.inbound.protection.outlook.com	AS8075 Microsoft Corporation AS8075 Microsoft Corporation AS8075 Microsoft Corporation AS8075 Microsoft Corporation AS8075 Microsoft Corporation AS8075 Microsoft Corporation AS8075 Microsoft Corporation AS8075 Microsoft Corporation

📧 Autodiscover / Autoconfig#

Service	CNAME / IP
🔷 Autodiscover	autodiscover.outlook.com → 40.104.116.56

🔷 AAAA Records (IPv6)#

✗ No AAAA records — IPv6 not configured

🔐 HTTPS Records#

✗ No HTTPS RR — no SVCB/HTTPS service binding

🔌 SRV Records#

1 records 427ms

Service	Priority	Weight	Port	Target
_sipfederationtls._tcp	0	0	5061	sipfed.online.lync.com

📝 TXT Records#

3 records 487ms

TXT Record
MS=C1DF851783D9965EF467C80611B883DDFF9A5130
MS=ms57222675
v=spf1 include:_spf2.bodata.dk include:spf.protection.outlook.com ~all

✉️ SPF#

Policy	Record (vildbjerg-cup.dk)
~all (soft fail)	v=spf1 include:_spf2.bodata.dk include:spf.protection.outlook.com ~all

📨 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

🧩 Web & zone#

latest probe, not this scan · checked 2026-10-14 08:58:29

www CNAME	vildbjerg-cup.kameli.dk (all on kameli.dk) → 37.35.100.21 (AS49974)
www vs bare domain	Same network vildbjerg-cup.dk: 37.35.100.21 (AS49974) www.vildbjerg-cup.dk: 37.35.100.21 (AS49974)
Wildcard	No

🔎 SPF check#

zone-wide SPF report

DNS lookups: 2/10 · policy: ~all

No problems found

🔗 TLSA / DANE#

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

🔐 DNSSEC#

437ms

Check	Result
Validation Status	🔓 Insecure
AD Flag (resolver validates)	✗ Not set
DS Record	✗ Not found
DNSKEY Record	✗ Not found
Flags	unsigned answer

🏷️ SOA#

32ms

Field	Value
Serial	2014010753
Primary NS (MNAME)	ns.bodata.dk
Responsible (RNAME)	admin@ns.bodata.dk
Refresh	7300s
Retry	1300s
Expire	1209600s
Minimum (neg-cache TTL)	86400s

📋 Registration#

WHOIS fetched 2026-10-14 16:30:19

Field	Value
Registrar	BO DATA ApS
Registered	1996-08-30
Expires	2027-09-30 (344d)

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

419ms

42ms

428ms

AAAA

415ms

TXT

487ms

CAA

33ms

HTTPS

415ms

TLSA

453ms

SOA

32ms

MTA-STS

432ms

DNSSEC

437ms

SRV

427ms

Total

1318ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-02 16:59:44	3420ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-29 16:39:35	621ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-27 04:55:30	1340ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-11 17:27:29	9882ms	2 NS 1 A 1 MX	🔓 Insecure
2026-07-13 00:11:23	33143ms	2 NS 1 A 1 MX	🔓 Insecure
2026-07-02 13:31:00 shown	1318ms	2 NS 1 A 1 MX	🔓 Insecure
2026-06-24 17:29:01	979ms	2 NS 1 A 1 MX	🔓 Insecure
2026-06-17 13:57:57	4766ms	2 NS 1 A 1 MX	🔓 Insecure