gls-app.dk

Records from scan: 2026-10-07 20:52:16 · 4271ms total · last checked 2026-10-19 13:29 (unchanged)

🧟 Lame delegation ⬇ Zone File 📜 Timeline & History ⚡ Scan Now

gls-app.dk is a registered .dk domain whose nameservers (pns.dtag.de, secondary006.dtag.net) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 7 December 2016 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. Below are all of its DNS records from our latest scan: nameservers, A/AAAA, MX, TXT, SPF, DMARC, CAA, TLSA/DANE, MTA-STS, SRV and more.

🖥️ Nameservers#

2 records 457ms

Nameserver	IP addresses	PTR	ASN / ISP
pns.dtag.de	194.25.0.125 2003:40:8000::100	pns.dtag.de pns.dtag.de	AS3320 Deutsche Telekom AG AS3320 Deutsche Telekom AG
secondary006.dtag.net	195.244.245.25 2a00:fa8:3:0:100:0:6:1	secondary006.dtag.net secondary006.dtag.net	AS5605 NetUSE AG AS5605 NetUSE AG

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

472ms

Check	Result
Validation Status	❓ Unknown (the delegated nameservers don't answer)
AD Flag (resolver validates)	✗ Not set
DS Record	✗ Not found
DNSKEY Record	✗ Not found
Flags	resolution failed: failure

🏷️ SOA#

✗ No SOA record found

📋 Registration#

WHOIS fetched 2026-10-19 14:32:28

Field	Value
Registrar	Deutsche Telekom AG
Registered	2016-12-07
Expires	2026-12-31 (72d)

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

457ms

452ms

454ms

AAAA

458ms

TXT

1947ms

CAA

449ms

HTTPS

459ms

TLSA

384ms

SOA

22ms

MTA-STS

406ms

DNSSEC

472ms

SRV

452ms

Total

4271ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-07 20:52:16 shown	4271ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-07 14:26:06	13280ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 07:01:00	4744ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 00:30:20	4163ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 00:16:24	7434ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 00:00:27	9717ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 22:21:05	8687ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 21:58:57	3832ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 20:15:05	2633ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 15:51:54	4670ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 03:16:12	2734ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 21:23:56	5452ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 21:13:10	2741ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 02:02:29	3988ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-03 03:03:14	2136ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-31 05:11:22	4845ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 21:38:17	5214ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 17:50:04	4145ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 15:22:06	35264ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 15:02:46	2683ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 14:51:21	13043ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 10:35:12	4767ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 04:39:58	12422ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 06:02:46	11039ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 02:12:22	4515ms	2 NS 0 A 0 MX	❓ Unknown