refreshit.dk

📜 Historical scan 2026-06-18 00:31:30  ·  ← Latest scan
⬇ Zone File 📜 Timeline & History ⚡ Scan Now

refreshit.dk is a .dk domain served by 2 nameservers (ns1.mydomain.com, ns2.mydomain.com). It was already in the .dk zone when our tracking began on 16 June 2026. Its website address 66.96.149.32 is hosted by Newfold Digital, Inc. (AS29873) in United States. Mail is handled by mx.refreshit.dk. The zone is not DNSSEC-signed, 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.

🖥️ Nameservers#

2 records   314ms

🌍 A Records#

1 records   259ms

📧 MX Records#

1 records   225ms

📧 Autodiscover / Autoconfig#

ServiceCNAME / IP
🔷 Autodiscover66.96.163.133
🔶 Autoconfig66.96.163.133

🔷 AAAA Records (IPv6)#

✗ No AAAA records — IPv6 not configured

🔐 HTTPS Records#

✗ No HTTPS RR — no SVCB/HTTPS service binding

📝 TXT Records#

1 records   4795ms
TXT Record
v=spf1 ip4:66.96.128.0/18 include:websitewelcome.com ?all

✉️ SPF#

PolicyRecord (refreshit.dk)
?all (neutral) v=spf1 ip4:66.96.128.0/18 include:websitewelcome.com ?all

📨 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-10-11 19:45:25
www66.96.149.32 (AS29873) (address records, no CNAME)
www vs bare domainSame network
refreshit.dk: 66.96.149.32 (AS29873)
www.refreshit.dk: 66.96.149.32 (AS29873)
WildcardYes: any name under the zone resolves

✍️ DKIM keys#

1 found
SelectorCNAMEKey
dkim cur.dkim.v.eigmail.net RSA · ~2048 bit test mode

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.

🔎 SPF check#

zone-wide SPF report

DNS lookups: 8/10 · policy: ?all

  • warn "?all" is neutral: it gives receivers no guidance, much like having no SPF
  • warn 8 of the 10 allowed DNS lookups used: one more include can break SPF

🔗 TLSA / DANE#

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

🔐 DNSSEC#

379ms
CheckResult
Validation Status🔓 Insecure
AD Flag (resolver validates)✗ Not set
DS Record✗ Not found
DNSKEY Record✗ Not found
Flagsunsigned answer

🏷️ SOA#

452ms
FieldValue
Serial2013011648
Primary NS (MNAME)ns1.mydomain.com
Responsible (RNAME)dnsadmin@mydomain.com
Refresh10800s
Retry3600s
Expire604800s
Minimum (neg-cache TTL)3600s

📋 Registration#

✗ No registration data yet — queued for a WHOIS lookup
📋 WHOIS#

⏱️ Lookup Timing#

NS
314ms
A
259ms
MX
225ms
AAAA
225ms
TXT
4795ms
CAA
303ms
HTTPS
479ms
TLSA
667ms
SOA
452ms
MTA-STS
466ms
DNSSEC
379ms
SRV
1214ms
Total
6427ms

🕐 Scan History#

Scanned AtDurationRecordsDNSSEC
2026-09-27 07:00:28 9897ms 2 NS 1 A 1 MX 🔓 Insecure
2026-09-12 09:53:26 1312ms 2 NS 1 A 1 MX 🔓 Insecure
2026-08-26 13:42:08 10393ms 2 NS 1 A 1 MX 🔓 Insecure
2026-07-24 00:14:10 23859ms 2 NS 1 A 1 MX 🔓 Insecure
2026-06-26 05:07:41 3078ms 2 NS 0 A 1 MX 🔓 Insecure
2026-06-23 22:49:55 4159ms 2 NS 1 A 1 MX 🔓 Insecure
2026-06-18 00:31:30 shown 6427ms 2 NS 1 A 1 MX 🔓 Insecure
dhd.dk [/] search Domains, Hosts & DNS — .dk zone