ledcity.be - robtex.com
ledcity.be
| DNSSEC | ⚠️ Not signed | ||||||
be
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.nsset.be ⭐ | ||||||
| NS | b.nsset.be | ||||||
| NS | c.nsset.be | ||||||
| NS | d.nsset.be | ||||||
| NS | y.nsset.be | ||||||
| NS | z.nsset.be | ||||||
| SOA | a.nsset.bebe-hostmaster@dnsbelgium.be serial=1028245018 | ||||||
Previously MX for
ledcity.be |
Same first word
Similar names
cityled.net |
delcity.mx |
cityled.com |
delcity.net |
delcity.com |
delcity.de |
citydle.com |
citydel.com |
cityled.ch |
cityled.cn |
delcity.gov |
cityled.uz |
cityled.at |
delcity.mu |
cityled.eu |
cytidel.com |
DNS History
12 records (0 active, 12 former)
○NSns0.transip.net2017-03-13 → 2020-03-22 · 5 obs
○ 2016-07-01 14:55:20
● 2017-03-13 01:28:10
● 2020-03-22 03:05:28
○ 2026-03-29 14:21:36
○ 2026-05-11 05:23:40
● 2017-03-13 01:28:10
● 2020-03-22 03:05:28
○ 2026-03-29 14:21:36
○ 2026-05-11 05:23:40
○NSns01.one.com2015-06-23 → 2016-07-01 · 4 obs
● 2015-06-23 16:20:26
● 2016-07-01 14:55:20
○ 2017-03-13 01:28:10
○ 2026-05-11 05:23:40
● 2016-07-01 14:55:20
○ 2017-03-13 01:28:10
○ 2026-05-11 05:23:40
○NSns02.one.com2015-06-23 → 2016-07-01 · 4 obs
● 2015-06-23 16:20:26
● 2016-07-01 14:55:20
○ 2017-03-13 01:28:10
○ 2026-05-11 05:23:40
● 2016-07-01 14:55:20
○ 2017-03-13 01:28:10
○ 2026-05-11 05:23:40
○NSns1.transip.nl2017-03-13 → 2020-03-22 · 5 obs
○ 2016-07-01 14:55:20
● 2017-03-13 01:28:10
● 2020-03-22 03:05:28
○ 2026-03-29 14:21:36
○ 2026-05-11 05:23:40
● 2017-03-13 01:28:10
● 2020-03-22 03:05:28
○ 2026-03-29 14:21:36
○ 2026-05-11 05:23:40
○NSns2.transip.eu2017-03-13 → 2020-03-22 · 5 obs
○ 2016-07-01 14:55:20
● 2017-03-13 01:28:10
● 2020-03-22 03:05:28
○ 2026-03-29 14:21:36
○ 2026-05-11 05:23:40
● 2017-03-13 01:28:10
● 2020-03-22 03:05:28
○ 2026-03-29 14:21:36
○ 2026-05-11 05:23:40
○MXledcity.be2017-03-13 → 2020-03-22 · 5 obs
○ 2016-07-01 14:55:20
● 2017-03-13 01:28:10
● 2020-03-22 03:05:28
○ 2026-03-29 14:21:36
○ 2026-05-11 05:23:40
● 2017-03-13 01:28:10
● 2020-03-22 03:05:28
○ 2026-03-29 14:21:36
○ 2026-05-11 05:23:40
○MXmxcluster1.one.com2015-06-23 → 2016-07-01 · 4 obs
● 2015-06-23 16:20:26
● 2016-07-01 14:55:20
○ 2017-03-13 01:28:10
○ 2026-05-11 05:23:40
● 2016-07-01 14:55:20
○ 2017-03-13 01:28:10
○ 2026-05-11 05:23:40
○MXmxcluster2.one.com2015-06-23 → 2016-07-01 · 4 obs
● 2015-06-23 16:20:26
● 2016-07-01 14:55:20
○ 2017-03-13 01:28:10
○ 2026-05-11 05:23:40
● 2016-07-01 14:55:20
○ 2017-03-13 01:28:10
○ 2026-05-11 05:23:40
○MXrelay.transip.nl2017-03-13 → 2020-03-22 · 5 obs
○ 2016-07-01 14:55:20
● 2017-03-13 01:28:10
● 2020-03-22 03:05:28
○ 2026-03-29 14:21:36
○ 2026-05-11 05:23:40
● 2017-03-13 01:28:10
● 2020-03-22 03:05:28
○ 2026-03-29 14:21:36
○ 2026-05-11 05:23:40
○A141.138.137.42017-03-13 → 2017-03-13 · 4 obs
○ 2016-07-01 14:55:20
● 2017-03-13 01:28:10
○ 2020-03-22 03:05:28
○ 2026-05-11 05:23:40
● 2017-03-13 01:28:10
○ 2020-03-22 03:05:28
○ 2026-05-11 05:23:40
○A149.210.228.2242020-03-22 → 2020-03-22 · 4 obs
○ 2017-03-13 01:28:10
● 2020-03-22 03:05:28
○ 2026-03-29 14:21:36
○ 2026-05-11 05:23:40
● 2020-03-22 03:05:28
○ 2026-03-29 14:21:36
○ 2026-05-11 05:23:40
○A46.30.211.322015-06-23 → 2016-07-01 · 4 obs
● 2015-06-23 16:20:26
● 2016-07-01 14:55:20
○ 2017-03-13 01:28:10
○ 2026-05-11 05:23:40
● 2016-07-01 14:55:20
○ 2017-03-13 01:28:10
○ 2026-05-11 05:23:40
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| be | a.nsset.be, b.nsset.be, c.nsset.be, d.nsset.be... | - |
✅ Authoritative Response
Server:194.0.6.1
NS records: a.nsset.be, b.nsset.be, c.nsset.be, d.nsset.be, y.nsset.be, z.nsset.be
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 414ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|