alisharifi.dk

Historical scan 2026-07-28 03:12:46  ·  ← Latest scan
Lame delegation Zone File Timeline & History Scan Now

alisharifi.dk is a registered .dk domain whose nameservers (ns1.simply.com, ns2.simply.com, ns3.simply.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 3 August 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#

3 records   117ms

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-10-24 14:45:25
www CNAME82ee0c8ebf72ae4c.vercel-dns-017.com (all on vercel-dns-017.com)
www vs bare domainSame network
alisharifi.dk: 76.76.21.21 (AS16509)
www.alisharifi.dk: 216.198.79.65 64.29.17.65 (AS16509)
WildcardNo
Denial of existenceNSEC zone can be walked (all names enumerable)
CDS / CDNSKEYPublished: key rollovers can be automated with the registry (RFC 7344/8078) 1 CDS, 1 CDNSKEY

TLSA / DANE#

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

DNSSEC#

253ms
CheckResult
Validation Status Unknown (the delegated nameservers don't answer)
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:58:47
FieldValue
RegistrarSimply.com A/S
Registered2025-08-03
Expires2027-08-02 (257d)

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
117ms
A
111ms
MX
116ms
AAAA
137ms
TXT
486ms
CAA
134ms
HTTPS
111ms
TLSA
113ms
SOA
47ms
MTA-STS
234ms
DNSSEC
253ms
SRV
212ms
Total
1379ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-10-24 14:45:25 389ms 3 NS 1 A 0 MX Insecure
2026-10-04 14:47:11 407ms 3 NS 1 A 0 MX Insecure
2026-09-21 02:59:41 1632ms 3 NS 1 A 0 MX Insecure
2026-08-19 04:54:08 13125ms 3 NS 1 A 0 MX Insecure
2026-08-17 02:35:36 9233ms 3 NS 0 A 0 MX Unknown
2026-08-15 10:59:20 10130ms 3 NS 0 A 0 MX Unknown
2026-08-10 03:14:09 1471ms 3 NS 0 A 0 MX Unknown
2026-08-09 02:13:18 1321ms 3 NS 0 A 0 MX Unknown
2026-08-03 20:59:11 1183ms 3 NS 0 A 0 MX Unknown
2026-07-28 03:12:46 shown 1379ms 3 NS 0 A 0 MX Unknown
2026-07-27 02:59:02 1347ms 3 NS 0 A 0 MX Unknown
2026-07-26 02:48:33 1205ms 3 NS 0 A 0 MX Unknown
2026-07-25 02:16:45 1401ms 3 NS 0 A 0 MX Unknown
2026-07-24 01:06:01 10158ms 3 NS 0 A 0 MX Unknown
2026-07-22 23:42:35 10146ms 3 NS 0 A 0 MX Unknown
2026-07-21 16:12:06 16805ms 3 NS 0 A 0 MX Unknown
2026-07-02 00:00:07 760ms 3 NS 1 A 1 MX Secure
2026-06-16 12:37:58 597ms 3 NS 1 A 1 MX Secure