getfound.dk

Historical scan 2026-06-22 07:22:45  ·  ← Latest scan
Zone File Timeline & History Scan Now

getfound.dk is a .dk domain served by 3 nameservers (ns1.azehosting.net, ns2.azehosting.net, ns3.azehosting.net). It was registered on 13 September 2021 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. Mail is handled by in1-smtp.messagingengine.com, in2-smtp.messagingengine.com. The zone is not DNSSEC-signed, publishes a DMARC policy and is reachable over IPv6. 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#

3 records   158ms

A Records#

1 records   133ms
IPTTLPTRASNISP / OrgCIDRCountryCity
162.55.97.110 3600s cp04.azehosting.net AS24940 — — — —

MX Records#

2 records   137ms

AAAA Records (IPv6)#

1 records   160ms
IPv6 AddressTTLPTRASNISP / OrgCIDRCountryCity
2a01:4f8:271:2a11::2 3600s cp04.azehosting.net AS24940 — — — —

HTTPS Records#

No HTTPS RR — no SVCB/HTTPS service binding

TXT Records#

1 records   556ms
TXT Record
v=spf1 ip4:162.55.97.110 include:spf.azehosting.net include:spf.messagingengine.com ?all

SPF#

PolicyRecord (getfound.dk)
?all (neutral) v=spf1 ip4:162.55.97.110 include:spf.azehosting.net include:spf.messagingengine.com ?all

DMARC#

PolicyRecord (_dmarc.getfound.dk)
p=none (monitor only) v=DMARC1; p=none;

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-07 04:25:10
www CNAMEgetfounddk.netlify.app (all on netlify.app)
www vs bare domainSame network
WildcardNo
Denial of existenceNSEC3 · 7 iterations · 8-byte salt RFC 9276 recommends 0 iterations and no salt
CDS / CDNSKEYNone 0 CDS, 0 CDNSKEY

DKIM keys#

1 found
SelectorCNAMEKey
default — RSA · ~2048 bit

DKIM selectors can't be listed, so we check the common ones (Microsoft 365, Google, Mailchimp, SendGrid, generic). Keys under other selectors aren't shown.

DNS lookups: 3/10 · policy: ?all

  • warn "?all" is neutral: it gives receivers no guidance, much like having no SPF

ACME Challenge#

TypeNameValue
TXT _acme-challenge.getfound.dk InxDCnpZ1LN6RPhK3rtr8r1pggy_aYj5b-Fpgu8FVc4

TLSA / DANE#

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

DNSSEC#

2083ms
CheckResult
Validation Status Insecure
AD Flag (resolver validates) Not set
DS Record Not found
DNSKEY Record Found
Flagsunsigned answer

SOA#

0ms
FieldValue
Serial2026062101
Primary NS (MNAME)ns1.azehosting.net
Responsible (RNAME)server-admin@azehosting.net
Refresh3600s
Retry1200s
Expire1209600s
Minimum (neg-cache TTL)86400s

Registration#

WHOIS fetched 2026-11-07 04:26:48
FieldValue
Registrar1API GmbH
Registered2021-09-13
Expires2027-09-30 (317d)
📋 WHOIS#

Lookup Timing#

NS
158ms
A
133ms
MX
137ms
AAAA
160ms
TXT
556ms
CAA
143ms
HTTPS
156ms
TLSA
127ms
SOA
0ms
MTA-STS
148ms
DNSSEC
2083ms
SRV
186ms
Total
2919ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-07 04:25:10 991ms 3 NS 1 A 2 MX Insecure
2026-10-24 16:04:53 1001ms 3 NS 1 A 2 MX Insecure
2026-10-23 02:28:40 2303ms 3 NS 1 A 2 MX Insecure
2026-10-22 00:20:25 1729ms 3 NS 1 A 2 MX Insecure
2026-10-21 20:12:00 2329ms 3 NS 1 A 2 MX Insecure
2026-10-07 16:07:25 707ms 3 NS 1 A 2 MX Insecure
2026-10-01 00:21:00 962ms 3 NS 1 A 2 MX Insecure
2026-09-29 01:09:46 1978ms 3 NS 1 A 2 MX Insecure
2026-08-28 15:46:00 1603ms 3 NS 1 A 2 MX Insecure
2026-08-26 13:59:55 9871ms 3 NS 1 A 2 MX Insecure
2026-08-22 16:16:36 8157ms 3 NS 1 A 2 MX Insecure
2026-06-30 18:55:02 1541ms 3 NS 1 A 2 MX Insecure
2026-06-22 07:22:45 shown 2919ms 3 NS 1 A 2 MX Insecure
2026-06-20 15:19:03 790ms 3 NS 1 A 2 MX Insecure
2026-06-17 09:34:52 2895ms 3 NS 1 A 2 MX Insecure