brixbridge.dk

Records from scan: 2026-10-09 11:30:33  ·  868ms total  ·  last checked 2026-10-19 03:09 (unchanged)
⬇ Zone File 📜 Timeline & History ⚡ Scan Now

brixbridge.dk is a .dk domain served by 2 nameservers (ns61.domaincontrol.com, ns62.domaincontrol.com). It was registered on 16 April 2024 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. Its website address 15.197.225.128 is hosted by Amazon.com, Inc. (AS16509) in United States. Mail is handled by mail.brixbridge.dk. The zone is not DNSSEC-signed, has no DMARC policy and has no IPv6 address. Below are all of its DNS records from our latest scan: nameservers, A/AAAA, MX, TXT, SPF, DMARC, CAA, TLSA/DANE, MTA-STS, SRV and more.

🖥️ Nameservers#

2 records   64ms

🌍 A Records#

2 records   46ms

📧 MX Records#

1 records   40ms
PriorityTTLMail ServerIP addressesPTRASN
5 1800s mail.brixbridge.dk 198.60.193.11 m11.wpx.net AS210250 K Media Tech Ltd.

🔷 AAAA Records (IPv6)#

✗ No AAAA records — IPv6 not configured

🔐 HTTPS Records#

✗ No HTTPS RR — no SVCB/HTTPS service binding

📝 TXT Records#

1 records   261ms
TXT Record
v=spf1 a mx a:brixbridge.dk ip4:198.60.193.11 ?all

✉️ SPF#

PolicyRecord (brixbridge.dk)
?all (neutral) v=spf1 a mx a:brixbridge.dk ip4:198.60.193.11 ?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#

checked 2026-10-09 11:30:33
wwwNXDOMAIN
www vs bare domainwww does not resolve
brixbridge.dk: 15.197.225.128 3.33.251.168 (AS16509)
www.brixbridge.dk: no address
(all like this)
WildcardNo

✍️ DKIM keys#

1 found
SelectorCNAMEKey
dkim dkim.wpx.net RSA · ~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.

🔎 SPF check#

zone-wide SPF report

DNS lookups: 3/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#

123ms
CheckResult
Validation Status🔓 Insecure
AD Flag (resolver validates)✗ Not set
DS Record✗ Not found
DNSKEY Record✗ Not found
Flagsunsigned answer

🏷️ SOA#

47ms
FieldValue
Serial2026093000
Primary NS (MNAME)ns61.domaincontrol.com
Responsible (RNAME)dns@jomax.net
Refresh28800s
Retry7200s
Expire604800s
Minimum (neg-cache TTL)600s

📋 Registration#

WHOIS fetched 2026-09-30 15:19:26
FieldValue
RegistrarSimply.com A/S
Registered2024-04-16
Expires2028-04-15 (543d)
📋 WHOIS#

⏱️ Lookup Timing#

NS
64ms
A
46ms
MX
40ms
AAAA
52ms
TXT
261ms
CAA
68ms
HTTPS
42ms
TLSA
95ms
SOA
47ms
MTA-STS
93ms
DNSSEC
123ms
SRV
89ms
Total
868ms

🕐 Scan History#

Scanned AtDurationRecordsDNSSEC
2026-10-09 11:30:33 shown 868ms 2 NS 2 A 1 MX 🔓 Insecure
2026-10-04 07:44:26 625ms 2 NS 2 A 1 MX 🔓 Insecure
2026-09-30 15:14:53 1779ms 2 NS 2 A 1 MX 🔓 Insecure
2026-09-29 15:10:26 1276ms 2 NS 2 A 1 MX 🔓 Insecure
2026-09-28 05:29:04 9734ms 2 NS 2 A 1 MX 🔓 Insecure
2026-09-20 20:10:03 9628ms 2 NS 2 A 1 MX 🔓 Insecure
2026-09-08 15:10:30 9742ms 2 NS 2 A 1 MX 🔓 Insecure
2026-09-04 09:21:03 2603ms 2 NS 2 A 1 MX 🔓 Insecure
2026-08-27 14:53:28 824ms 2 NS 2 A 1 MX 🔓 Insecure
2026-08-26 16:16:35 1102ms 2 NS 2 A 1 MX 🔓 Insecure
2026-07-09 06:19:05 1396ms 2 NS 2 A 1 MX 🔓 Insecure
2026-06-25 08:09:19 1674ms 2 NS 2 A 1 MX 🔓 Insecure
2026-06-24 15:41:54 2347ms 2 NS 2 A 1 MX 🔓 Insecure
2026-06-23 14:41:46 713ms 2 NS 2 A 1 MX 🔓 Insecure
2026-06-21 07:45:05 710ms 2 NS 2 A 1 MX 🔓 Insecure
2026-06-21 06:32:09 919ms 0 NS 0 A 0 MX ❓ Unknown
2026-06-20 07:36:51 760ms 2 NS 2 A 1 MX 🔓 Insecure
2026-06-20 02:34:43 622ms 2 NS 2 A 1 MX 🔓 Insecure
2026-06-16 17:17:52 1581ms 2 NS 2 A 1 MX 🔓 Insecure
2026-06-16 17:17:45 3864ms 2 NS 2 A 1 MX 🔓 Insecure
2026-06-16 17:08:31 540ms 2 NS 2 A 1 MX 🔓 Insecure
2026-06-16 17:00:09 610ms 2 NS 2 A 1 MX 🔓 Insecure
dhd.dk [/] search Domains, Hosts & DNS — .dk zone