mesinge-tømren.dk xn--mesinge-tmren-jnb.dk

Records from scan: 2026-09-30 08:22:30  ·  23614ms total  ·  last checked 2026-11-17 05:29 (unchanged)
Zone File Timeline & History Scan Now

mesinge-tømren.dk is a .dk domain served by 3 nameservers (ns1.mono.net, ns2.mono.net, ns3.mono.net). It was registered on 7 March 2014 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. The zone is of unknown DNSSEC status, 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#

3 records   2058ms

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#

checked 2026-11-12 05:17:09
www CNAMExn--mesinge-tmren-jnb.dk (all on xn--mesinge-tmren-jnb.dk)
www vs bare domainSame network
mesinge-tømren.dk: 185.58.213.13 (AS201595)
www.mesinge-tømren.dk: 185.58.213.13 (AS201595)
WildcardNo

TLSA / DANE#

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

DNSSEC#

10062ms
CheckResult
Validation Status Unknown
AD Flag (resolver validates) Not set
DS Record Not found
DNSKEY Record Not found
Flagsresolution failed: timed out

SOA#

0ms
FieldValue
Serial2026070601
Primary NS (MNAME)ns1.mono.net
Responsible (RNAME)domains@mono.net
Refresh300s
Retry60s
Expire1209600s
Minimum (neg-cache TTL)3600s

Registration#

WHOIS fetched 2026-11-16 02:18:50
FieldValue
RegistrarPunktum dk A/S (direct)
Registered2014-03-07
Expires2027-03-31 (132d)

Same registrant#

0 domains

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
📋 WHOIS#

Lookup Timing#

NS
2058ms
A
4038ms
MX
4030ms
AAAA
2336ms
TXT
19226ms
CAA
4043ms
HTTPS
4038ms
TLSA
4028ms
SOA
0ms
MTA-STS
4035ms
DNSSEC
10062ms
SRV
4048ms
Total
23614ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-09-30 08:22:30 shown 23614ms 3 NS 0 A 0 MX Unknown
2026-09-10 00:19:35 34388ms 3 NS 0 A 1 MX Unknown
2026-08-24 20:16:29 33419ms 3 NS 1 A 1 MX Insecure
2026-08-15 04:24:36 25477ms 3 NS 1 A 1 MX Insecure
2026-07-07 02:45:42 8966ms 3 NS 1 A 1 MX Insecure
2026-06-30 20:11:08 20106ms 3 NS 1 A 0 MX Insecure
2026-06-22 22:57:52 3032ms 3 NS 1 A 1 MX Unknown
2026-06-21 10:11:37 307ms 0 NS 0 A 0 MX Secure
2026-06-21 09:31:15 4962ms 3 NS 1 A 1 MX Secure
2026-06-21 03:42:08 299ms 0 NS 0 A 0 MX Secure
2026-06-19 04:53:12 375ms 0 NS 0 A 0 MX Secure
2026-06-18 03:41:46 2765ms 3 NS 1 A 1 MX Secure