tjklub.dk is a .dk domain served by 4 nameservers (ns1-36.azure-dns.com, ns2-36.azure-dns.net, ns3-36.azure-dns.org and 1 more). It was registered on 2 November 2022 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. Its website address 20.82.13.59 is hosted by Microsoft Corporation (AS8075) in The Netherlands. Mail is handled by tjklub-dk.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 our latest scan: nameservers, A/AAAA, MX, TXT, SPF, DMARC, CAA, TLSA/DANE, MTA-STS, SRV and more.
| IP | TTL | PTR | ASN | ISP / Org | CIDR | Country | City |
|---|---|---|---|---|---|---|---|
| 20.82.13.59 | 3600s | — | AS8075 | Microsoft Corporation | 20.64.0.0/10 | 🇳🇱 The Netherlands | Amsterdam |
| Service | CNAME / IP |
|---|---|
| 🔷 Autodiscover | autodiscover.outlook.com → 40.104.116.24 |
| TXT Record |
|---|
| 65bvpqhwwdbpykb5d86l7kmmx210042r |
| v=spf1 include:spf.protection.outlook.com -all |
| Policy | Record (tjklub.dk) |
|---|---|
| -all (hard fail) | v=spf1 include:spf.protection.outlook.com -all |
| www | Address record (no CNAME) |
| Wildcard | No |
DNS lookups: 1/10 · policy: -all
No problems found| Check | Result |
|---|---|
| Validation Status | 🔓 Insecure |
| AD Flag (resolver validates) | ✗ Not set |
| DS Record | ✗ Not found |
| DNSKEY Record | ✗ Not found |
| Flags | unsigned answer |
| Field | Value |
|---|---|
| Serial | 1 |
| Primary NS (MNAME) | ns1-36.azure-dns.com |
| Responsible (RNAME) | azuredns-hostmaster@microsoft.com |
| Refresh | 3600s |
| Retry | 300s |
| Expire | 2419200s |
| Minimum (neg-cache TTL) | 300s |
| Field | Value |
|---|---|
| Registrar | Punktum dk A/S (direct) |
| Registered | 2022-11-02 |
| Expires | 2026-11-01 (14d) |
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-01 03:18:14 shown | 1455ms | 4 NS 1 A 1 MX | 🔓 Insecure |
| 2026-09-30 06:23:22 | 782ms | 4 NS 1 A 1 MX | 🔓 Insecure |
| 2026-09-26 14:15:47 | 3203ms | 4 NS 1 A 1 MX | 🔓 Insecure |
| 2026-09-01 18:11:37 | 9801ms | 4 NS 1 A 1 MX | 🔓 Insecure |
| 2026-06-24 18:21:06 | 1101ms | 4 NS 1 A 1 MX | 🔓 Insecure |
| 2026-06-22 16:34:39 | 1144ms | 0 NS 0 A 0 MX | ❓ Unknown |
| 2026-06-17 13:38:52 | 3938ms | 4 NS 1 A 1 MX | 🔓 Insecure |