bro-kommunikation.dk

Historical scan 2026-08-03 15:48:43  ·  ← Latest scan
Zone File Timeline & History Scan Now

bro-kommunikation.dk is a .dk domain served by 2 nameservers (ns01.one.com, ns02.one.com). It was registered on 22 November 2000 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. Its website address 94.231.103.162 is hosted by team.blue Denmark A/S (AS48854) in Denmark. Mail is handled by wearebro-dk.mx1-dk.mailanyone.net. The zone is DNSSEC-signed and validates, 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   77ms

A Records#

1 records   76ms

MX Records#

1 records   57ms

Autodiscover / Autoconfig#

ServiceCNAME / IP
🔷 Autodiscover62.116.223.34

AAAA Records (IPv6)#

No AAAA records — IPv6 not configured

HTTPS Records#

No HTTPS RR — no SVCB/HTTPS service binding

TXT Records#

2 records   157ms
TXT Record
MS=ms36267853
v=spf1 include:servers.mcsv.net ?all

SPF#

PolicyRecord (bro-kommunikation.dk)
?all (neutral) v=spf1 include:servers.mcsv.net ?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-11-07 01:09:34
www94.231.103.162 (AS48854) (address records, no CNAME)
www vs bare domainSame network
bro-kommunikation.dk: 94.231.103.162 (AS48854)
www.bro-kommunikation.dk: 94.231.103.162 (AS48854)
WildcardNo
Denial of existenceNSEC3 · 0 iterations · no salt RFC 9276 ✓
CDS / CDNSKEYNone 0 CDS, 0 CDNSKEY

DKIM keys#

1 found
SelectorCNAMEKey
k1 dkim.mcsv.net RSA · ~1024 bit below 2048 bit

DKIM selectors can't be listed, so we check the common ones (Microsoft 365, Google, Mailchimp, SendGrid, generic). Keys under other selectors aren't shown.

DNS lookups: 1/10 · policy: ?all

  • warn "?all" is neutral: it gives receivers no guidance, much like having no SPF

TLSA / DANE#

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

DNSSEC#

210ms
CheckResult
Validation Status Secure
AD Flag (resolver validates) Set
DS Record Found
DNSKEY Record Found
Flagsfully validated

SOA#

0ms
FieldValue
Serial2026080201
Primary NS (MNAME)ns01.one.com
Responsible (RNAME)hostmaster@one.com
Refresh14400s
Retry3600s
Expire1209600s
Minimum (neg-cache TTL)600s

Registration#

WHOIS fetched 2026-11-06 01:14:53
FieldValue
RegistrarPunktum dk A/S (direct)
Registered2000-11-22
Expires2026-12-31 (42d)

Same registrant#

28 domains
📋 WHOIS#

Lookup Timing#

NS
77ms
A
76ms
MX
57ms
AAAA
57ms
TXT
157ms
CAA
76ms
HTTPS
78ms
TLSA
98ms
SOA
0ms
MTA-STS
77ms
DNSSEC
210ms
SRV
86ms
Total
1218ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-07 01:09:34 659ms 2 NS 1 A 1 MX Secure
2026-10-10 12:08:25 2083ms 2 NS 1 A 1 MX Secure
2026-10-04 11:17:40 539ms 2 NS 1 A 1 MX Secure
2026-09-30 11:10:01 724ms 2 NS 1 A 1 MX Secure
2026-09-27 03:57:13 551ms 2 NS 1 A 1 MX Secure
2026-09-07 03:57:19 933ms 2 NS 1 A 1 MX Secure
2026-08-11 09:59:53 915ms 2 NS 1 A 1 MX Secure
2026-08-03 15:48:43 shown 1218ms 2 NS 1 A 1 MX Secure
2026-07-17 13:35:50 4823ms 2 NS 1 A 1 MX Secure
2026-07-02 14:44:55 9632ms 2 NS 1 A 1 MX Secure
2026-06-25 11:23:25 669ms 2 NS 1 A 1 MX Secure
2026-06-22 02:45:04 993ms 0 NS 0 A 0 MX Unknown
2026-06-20 22:37:54 1919ms 2 NS 1 A 1 MX Secure
2026-06-16 17:20:21 3023ms 2 NS 1 A 1 MX Secure
2026-06-16 17:07:10 409ms 2 NS 1 A 1 MX Secure
2026-06-16 17:02:42 1432ms 2 NS 1 A 1 MX Secure
2026-06-16 17:01:14 526ms 2 NS 1 A 1 MX Secure