invoro.dk

Historical scan 2026-06-22 14:01:55  ·  ← Latest scan
Zone File Timeline & History Scan Now

invoro.dk is a .dk domain with no delegation in this scan. It was registered on 1 September 2025 (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-13 00:23:05
www91.98.15.158 2a01:4f8:c01e:3fcc::1 (AS24940) (address records, no CNAME)
www vs bare domainSame network
WildcardYes: any name under the zone resolves
Denial of existenceNSEC3 · 0 iterations · no salt RFC 9276 ✓
CDS / CDNSKEYPublished: key rollovers can be automated with the registry (RFC 7344/8078) 2 CDS, 1 CDNSKEY

TLSA / DANE#

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

DNSSEC#

292ms
CheckResult
Validation StatusNot 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
Flagsresolution failed: failure

SOA#

No SOA record found

Registration#

WHOIS fetched 2026-11-06 03:46:18
FieldValue
RegistrarPunktum dk A/S (direct)
Registered2025-09-01
Expires2027-08-31 (287d)

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
184ms
A
173ms
MX
214ms
AAAA
183ms
TXT
271ms
CAA
207ms
HTTPS
201ms
TLSA
17ms
SOA
203ms
MTA-STS
218ms
DNSSEC
292ms
SRV
211ms
Total
987ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-13 00:23:05 746ms 2 NS 1 A 1 MX Secure
2026-11-11 20:44:45 726ms 2 NS 1 A 1 MX Secure
2026-11-06 03:23:12 977ms 2 NS 1 A 1 MX Secure
2026-10-30 02:51:29 899ms 2 NS 1 A 1 MX Secure
2026-10-24 16:12:51 1881ms 2 NS 1 A 1 MX Secure
2026-10-17 13:04:43 1171ms 2 NS 1 A 1 MX Secure
2026-10-10 01:54:05 1431ms 2 NS 1 A 1 MX Secure
2026-10-07 20:56:02 675ms 2 NS 1 A 1 MX Secure
2026-10-02 16:02:29 782ms 2 NS 1 A 1 MX Secure
2026-09-30 15:54:37 961ms 2 NS 1 A 1 MX Secure
2026-09-25 19:25:05 1142ms 2 NS 1 A 1 MX Secure
2026-09-24 19:08:10 9559ms 2 NS 1 A 1 MX Secure
2026-09-23 19:31:34 909ms 2 NS 1 A 1 MX Secure
2026-09-16 21:55:17 4150ms 2 NS 1 A 1 MX Secure
2026-09-14 20:48:27 1019ms 2 NS 1 A 1 MX Secure
2026-09-06 20:01:43 1649ms 2 NS 1 A 1 MX Secure
2026-08-29 17:16:36 1067ms 2 NS 1 A 1 MX Secure
2026-08-27 23:34:03 1232ms 2 NS 1 A 0 MX Secure
2026-08-27 13:20:18 2315ms 2 NS 1 A 0 MX Insecure
2026-08-26 12:36:27 2693ms 2 NS 1 A 0 MX Insecure
2026-08-21 15:31:53 9869ms 2 NS 1 A 0 MX Insecure
2026-08-17 20:00:31 9820ms 2 NS 1 A 0 MX Insecure
2026-08-13 13:24:00 3554ms 2 NS 1 A 0 MX Insecure
2026-08-08 02:27:00 976ms 2 NS 1 A 0 MX Insecure
2026-07-31 19:41:03 1143ms 2 NS 1 A 0 MX Insecure