keriome63.in - robtex.com
keriome63.in
| DNSSEC | ⚠️ Not signed | ||||||
in
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns01.trs-dns.com ⭐ | ||||||
| NS | ns.trs-dns.com | ||||||
| NS | ns01.trs-dns.net | ||||||
| NS | ns1.registry.in ⚠️ Not in parent delegation | ||||||
| NS | ns10.trs-dns.info | ||||||
| NS | ns10.trs-dns.org | ||||||
| NS | ns2.registry.in ⚠️ Not in parent delegation | ||||||
| NS | ns3.registry.in ⚠️ Not in parent delegation | ||||||
| NS | ns4.registry.in ⚠️ Not in parent delegation | ||||||
| SOA | ns.trs-dns.comtrs-ops@tucows.com serial=1778384461 | ||||||
Previously MX for
keriome63.in |
DNS History
12 records (0 active, 12 former)
○NSns1.bitcommand.com2017-03-19 → 2017-03-19 · 4 obs
○ 2016-07-09 14:57:22
● 2017-03-19 01:30:18
○ 2020-01-01 18:24:16
○ 2026-05-10 04:06:16
● 2017-03-19 01:30:18
○ 2020-01-01 18:24:16
○ 2026-05-10 04:06:16
○NSns1.chinbazar.com2015-07-14 → 2015-07-14 · 3 obs
● 2015-07-14 23:57:44
○ 2016-03-11 00:57:48
○ 2026-05-10 04:06:16
○ 2016-03-11 00:57:48
○ 2026-05-10 04:06:16
○NSns1.net-iran.com2016-07-09 → 2016-07-09 · 4 obs
○ 2016-03-11 00:57:48
● 2016-07-09 14:57:22
○ 2017-03-19 01:30:18
○ 2026-05-10 04:06:16
● 2016-07-09 14:57:22
○ 2017-03-19 01:30:18
○ 2026-05-10 04:06:16
○NSns2.bitcommand.com2017-03-19 → 2017-03-19 · 4 obs
○ 2016-07-09 14:57:22
● 2017-03-19 01:30:18
○ 2020-01-01 18:24:16
○ 2026-05-10 04:06:16
● 2017-03-19 01:30:18
○ 2020-01-01 18:24:16
○ 2026-05-10 04:06:16
○NSns2.chinbazar.com2015-07-14 → 2015-07-14 · 3 obs
● 2015-07-14 23:57:44
○ 2016-03-11 00:57:48
○ 2026-05-10 04:06:16
○ 2016-03-11 00:57:48
○ 2026-05-10 04:06:16
○NSns2.net-iran.com2016-07-09 → 2016-07-09 · 4 obs
○ 2016-03-11 00:57:48
● 2016-07-09 14:57:22
○ 2017-03-19 01:30:18
○ 2026-05-10 04:06:16
● 2016-07-09 14:57:22
○ 2017-03-19 01:30:18
○ 2026-05-10 04:06:16
○MXkeriome63.in2015-07-14 → 2015-07-14 · 3 obs
● 2015-07-14 23:57:44
○ 2016-03-11 00:57:48
○ 2026-05-10 04:06:16
○ 2016-03-11 00:57:48
○ 2026-05-10 04:06:16
○MXmail.keriome63.in2016-07-09 → 2017-03-19 · 5 obs
○ 2016-03-11 00:57:48
● 2016-07-09 14:57:22
● 2017-03-19 01:30:18
○ 2020-01-01 18:24:16
○ 2026-05-10 04:06:16
● 2016-07-09 14:57:22
● 2017-03-19 01:30:18
○ 2020-01-01 18:24:16
○ 2026-05-10 04:06:16
○A130.185.76.1012017-03-19 → 2017-03-19 · 4 obs
○ 2016-07-09 14:57:22
● 2017-03-19 01:30:18
○ 2020-01-01 18:24:16
○ 2026-05-10 04:06:16
● 2017-03-19 01:30:18
○ 2020-01-01 18:24:16
○ 2026-05-10 04:06:16
○A176.9.7.752015-07-14 → 2015-07-14 · 3 obs
● 2015-07-14 23:57:44
○ 2015-11-13 04:04:46
○ 2026-05-10 04:06:16
○ 2015-11-13 04:04:46
○ 2026-05-10 04:06:16
○A185.105.236.2042016-07-09 → 2016-07-09 · 4 obs
○ 2016-03-11 00:57:48
● 2016-07-09 14:57:22
○ 2017-03-19 01:30:18
○ 2026-05-10 04:06:16
● 2016-07-09 14:57:22
○ 2017-03-19 01:30:18
○ 2026-05-10 04:06:16
○A8.5.1.582015-11-13 → 2015-11-13 · 4 obs
○ 2015-07-14 23:57:44
● 2015-11-13 04:04:46
○ 2016-03-11 00:57:48
○ 2026-05-10 04:06:16
● 2015-11-13 04:04:46
○ 2016-03-11 00:57:48
○ 2026-05-10 04:06:16
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| in | ns10.trs-dns.org, ns01.trs-dns.com, ns10.trs-dns.info, ns01.trs-dns.net | - |
✅ Authoritative Response
Server:64.78.205.1
NS records: ns10.trs-dns.org, ns01.trs-dns.com, ns10.trs-dns.info, ns01.trs-dns.net
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 116ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|