no-fo.dk

📜 Historical scan 2026-07-02 20:31:26 · ← Latest scan

⬇ Zone File 📜 Timeline & History ⚡ Scan Now

no-fo.dk is a .dk domain served by 2 nameservers (ns02.one.com, ns1.mail.barbeque.tech). It was registered on 22 January 2015 (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 this scan: nameservers, A/AAAA, MX, TXT, SPF, DMARC, CAA, TLSA/DANE, MTA-STS, SRV and more.

🖥️ Nameservers#

2 records 4052ms

Nameserver	IP addresses	PTR	ASN / ISP
ns02.one.com	185.10.11.10 2001:67c:3c0::10	ns02.one.com ns02.one.com	AS51468 One.com A/S AS51468 One.com A/S
ns1.mail.barbeque.tech	188.166.33.138	mail.barbeque.tech	AS14061 DigitalOcean, LLC

🌍 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

🔗 TLSA / DANE#

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

🔐 DNSSEC#

10146ms

Check	Result
Validation Status	❓ Unknown
AD Flag (resolver validates)	✗ Not set
DS Record	✗ Not found
DNSKEY Record	✗ Not found
Flags	resolution failed: timed out

🏷️ SOA#

✗ No SOA record found

📋 Registration#

WHOIS fetched 2026-10-14 19:34:55

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2015-01-22
Expires	2027-01-31 (101d)

🔗 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#

4052ms

4075ms

4033ms

AAAA

4081ms

TXT

12283ms

CAA

4059ms

HTTPS

4046ms

TLSA

122ms

SOA

4036ms

MTA-STS

4055ms

DNSSEC

10146ms

SRV

4078ms

Total

13796ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-07 16:52:19	27274ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-30 16:03:34	2161ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-28 01:56:49	2222ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-28 04:19:10	11375ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 10:00:05	3439ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 09:32:32	11761ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 09:20:13	11161ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 08:25:51	6698ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 07:32:05	11311ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 06:57:33	3716ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 18:35:49	5994ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 10:21:25	4550ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 09:13:56	2524ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 08:14:35	11158ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 18:39:04	4748ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 11:27:21	18047ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 08:58:01	2501ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-30 04:51:50	11516ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 00:38:34	10584ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 12:10:57	1473ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 11:54:08	9204ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 11:07:29	9270ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 10:22:54	2449ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 09:30:54	9388ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 06:09:12	1960ms	2 NS 0 A 0 MX	❓ Unknown