bluegaz.dk is a .dk domain served by 2 nameservers (ns01.one.com, ns02.one.com). It was registered on 15 January 2024 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. Mail is handled by bluegaz-dk.mail.protection.outlook.com. The zone is DNSSEC-signed but currently fails validation, 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.
| Nameserver | IP addresses | PTR | ASN / ISP |
|---|---|---|---|
| ns01.one.com | — | — | — |
| ns02.one.com | — | — | — |
| IP | TTL | PTR | ASN | ISP / Org | CIDR | Country | City |
|---|---|---|---|---|---|---|---|
| 178.73.217.13 | — | www.bluegaz.se | AS42708 | — | — | — | Falkenberg |
| TXT Record |
|---|
| MS=ms77520298 |
| v=spf1 include:spf.protection.outlook.com -all |
| Policy | Record (bluegaz.dk) |
|---|---|
| -all (hard fail) | v=spf1 include:spf.protection.outlook.com -all |
| www | 104.21.52.6 172.67.192.197 2606:4700:3031::6815:3406 2606:4700:3036::ac43:c0c5 (AS13335) (address records, no CNAME) |
| www vs bare domain | Same network |
| Wildcard | No |
DNS lookups: 1/10 · policy: -all
No problems found| Check | Result |
|---|---|
| Validation Status | ⚠️ Bogus |
| AD Flag (resolver validates) | ✗ Not set |
| DS Record | ✓ Found |
| DNSKEY Record | ✓ Found |
| Flags | resolution failed: insecurity proof failed |
| Field | Value |
|---|---|
| Serial | 2026053001 |
| Primary NS (MNAME) | ns01.one.com |
| Responsible (RNAME) | hostmaster@one.com |
| Refresh | 14400s |
| Retry | 3600s |
| Expire | 1209600s |
| Minimum (neg-cache TTL) | 600s |
| Field | Value |
|---|---|
| Registrar | ONE.COM A/S |
| Registered | 2024-01-15 |
| Expires | 2027-01-14 (78d) |
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| Scanned At | Duration | Records | DNSSEC |
|---|---|---|---|
| 2026-10-14 10:43:56 | 3910ms | 2 NS 2 A 1 MX | 🔓 Insecure |
| 2026-10-13 10:20:11 | 1549ms | 2 NS 2 A 1 MX | 🔓 Insecure |
| 2026-10-03 04:16:49 | 1526ms | 2 NS 1 A 1 MX | 🔒 Secure |
| 2026-09-09 05:28:59 | 1768ms | 2 NS 1 A 1 MX | 🔒 Secure |
| 2026-08-07 05:03:08 | 1302ms | 2 NS 1 A 1 MX | 🔒 Secure |
| 2026-07-03 15:04:45 | 3617ms | 2 NS 1 A 1 MX | 🔒 Secure |
| 2026-06-23 17:44:39 | 672ms | 2 NS 1 A 1 MX | 🔒 Secure |
| 2026-06-23 06:41:01 | 1150ms | 0 NS 0 A 0 MX | ❓ Unknown |
| 2026-06-16 15:07:53 | 3392ms | 2 NS 1 A 1 MX | 🔒 Secure |
| 2026-06-16 15:05:19 shown | 899ms | 2 NS 1 A 1 MX | ⚠️ Bogus |
| 2026-06-16 15:04:09 | 1752ms | 2 NS 1 A 1 MX | ⚠️ Bogus |
| 2026-06-16 15:00:50 | 695ms | 2 NS 1 A 1 MX | 🔒 Secure |