brianbager.dk
Historical scan 2026-06-21 05:32:24 · ← Latest scan
brianbager.dk is a .dk domain with no delegation in this scan. It was registered on 5 February 2011 (WHOIS) and 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#
No NS records found
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
Web & zone#
latest probe, not this scan · checked 2026-11-04 18:41:34| www | 46.30.213.144 2a02:2350:5:10c:86:c4e1:cb49:41e8 (AS51468) (address records, no CNAME) |
| www vs bare domain | Same network brianbager.dk: 46.30.213.144 2a02:2350:5:10c:86:c4e1:cb49:41e8 (AS51468) www.brianbager.dk: 46.30.213.144 2a02:2350:5:10c:86:c4e1:cb49:41e8 (AS51468) |
| Wildcard | No |
| Denial of existence | NSEC3 · 0 iterations · no salt RFC 9276 ✓ |
| CDS / CDNSKEY | None 0 CDS, 0 CDNSKEY |
TLSA / DANE#
No TLSA records — DANE not configured for HTTPS (_443) or MX (_25)
DNSSEC#
455ms| Check | Result |
|---|---|
| Validation Status | Not applicable: the domain has no delegation, so there is no zone to validate (stored verdict: Unknown). |
| AD Flag (resolver validates) | Not set |
| DS Record | Not found |
| DNSKEY Record | Not found |
| Flags | resolution failed: failure |
SOA#
No SOA record found
Registration#
WHOIS fetched 2026-10-23 12:01:44| Field | Value |
|---|---|
| Registrar | ONE.COM A/S |
| Registered | 2011-02-05 |
| Expires | 2027-02-28 (97d) |
Same registrant#
0 domainsOther .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#
NS
A
MX
AAAA
TXT
CAA
HTTPS
TLSA
SOA
MTA-STS
DNSSEC
SRV
Total
Scan History#
| Scanned At | Duration | Records | DNSSEC |
|---|---|---|---|
| 2026-11-04 18:41:34 | 605ms | 2 NS 1 A 4 MX | Secure |
| 2026-11-01 08:20:06 | 588ms | 2 NS 1 A 4 MX | Secure |
| 2026-10-23 11:45:35 | 485ms | 2 NS 1 A 4 MX | Secure |
| 2026-10-01 21:10:00 | 917ms | 2 NS 1 A 4 MX | Secure |
| 2026-09-29 20:54:36 | 511ms | 2 NS 1 A 4 MX | Secure |
| 2026-09-23 23:17:09 | 776ms | 2 NS 1 A 4 MX | Secure |
| 2026-09-08 17:33:18 | 1279ms | 2 NS 1 A 4 MX | Secure |
| 2026-08-31 22:36:11 | 540ms | 2 NS 1 A 4 MX | Secure |
| 2026-08-28 04:19:31 | 859ms | 2 NS 1 A 4 MX | Secure |
| 2026-08-23 12:51:06 | 878ms | 2 NS 1 A 4 MX | Secure |
| 2026-08-07 08:55:33 | 852ms | 2 NS 1 A 4 MX | Secure |
| 2026-08-03 22:12:38 | 1951ms | 2 NS 1 A 4 MX | Secure |
| 2026-07-16 12:42:26 | 6750ms | 2 NS 1 A 4 MX | Secure |
| 2026-06-30 06:18:31 | 926ms | 2 NS 1 A 4 MX | Secure |
| 2026-06-24 11:28:51 | 684ms | 2 NS 1 A 4 MX | Bogus |
| 2026-06-21 19:12:23 | 6127ms | 2 NS 1 A 4 MX | Secure |
| 2026-06-21 06:21:01 | 1132ms | 0 NS 0 A 0 MX | Unknown |
| 2026-06-21 05:32:24 shown | 1170ms | 0 NS 0 A 0 MX | Unknown |
| 2026-06-16 16:50:40 | 2584ms | 2 NS 1 A 4 MX | Secure |