533.in - robtex.com
533.in
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.dyna-ns.net ⚠️ Not in zone NS records | ||||||
| A | 2400:cb00:2049:1::a29f:1a5c🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 2400:cb00:2049:1::a29f:1b9e🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 162.159.26.92Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns1.dyna-ns.net | ||||||
| A | 162.159.27.158Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns1.dyna-ns.net | ||||||
| NS | ns2.dyna-ns.net ⚠️ Not in zone NS records | ||||||
| A | 2400:cb00:2049:1::a29f:1805🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 2400:cb00:2049:1::a29f:1905🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 162.159.24.5Cloudflare162.159.24.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns2.dyna-ns.net | ||||||
| A | 162.159.25.5Cloudflare162.159.25.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns2.dyna-ns.net | ||||||
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=1776252063 | ||||||
Same first word
Similar names
DNS History
12 records (2 active, 10 former)
○NS1170615778.earth.orderbox-dns.com2016-03-17 → 2017-08-22 · 5 obs
○ 2015-12-14 22:38:06
● 2016-03-17 06:43:20
● 2017-08-22 14:42:54
○ 2026-04-08 23:45:52
○ 2026-04-15 11:46:32
● 2016-03-17 06:43:20
● 2017-08-22 14:42:54
○ 2026-04-08 23:45:52
○ 2026-04-15 11:46:32
○NS1170615778.mars.orderbox-dns.com2016-03-17 → 2017-08-22 · 5 obs
○ 2015-12-14 22:38:06
● 2016-03-17 06:43:20
● 2017-08-22 14:42:54
○ 2026-04-08 23:45:52
○ 2026-04-15 11:46:32
● 2016-03-17 06:43:20
● 2017-08-22 14:42:54
○ 2026-04-08 23:45:52
○ 2026-04-15 11:46:32
○NS1170615778.mercury.orderbox-dns.com2016-03-17 → 2017-08-22 · 5 obs
○ 2015-12-14 22:38:06
● 2016-03-17 06:43:20
● 2017-08-22 14:42:54
○ 2026-04-08 23:45:52
○ 2026-04-15 11:46:32
● 2016-03-17 06:43:20
● 2017-08-22 14:42:54
○ 2026-04-08 23:45:52
○ 2026-04-15 11:46:32
○NS1170615778.venus.orderbox-dns.com2016-03-17 → 2017-08-22 · 5 obs
○ 2015-12-14 22:38:06
● 2016-03-17 06:43:20
● 2017-08-22 14:42:54
○ 2026-04-08 23:45:52
○ 2026-04-15 11:46:32
● 2016-03-17 06:43:20
● 2017-08-22 14:42:54
○ 2026-04-08 23:45:52
○ 2026-04-15 11:46:32
●NSns1.dyna-ns.net2026-04-08 → 2026-04-15 · 3 obs
○ 2017-08-22 14:42:54
● 2026-04-08 23:45:52
● 2026-04-15 11:46:32
● 2026-04-08 23:45:52
● 2026-04-15 11:46:32
○NSns1.parkingcrew.net2015-08-21 → 2015-12-14 · 4 obs
● 2015-08-21 19:09:52
● 2015-12-14 22:38:06
○ 2016-03-17 06:43:20
○ 2026-04-15 11:46:32
● 2015-12-14 22:38:06
○ 2016-03-17 06:43:20
○ 2026-04-15 11:46:32
●NSns2.dyna-ns.net2026-04-08 → 2026-04-15 · 3 obs
○ 2017-08-22 14:42:54
● 2026-04-08 23:45:52
● 2026-04-15 11:46:32
● 2026-04-08 23:45:52
● 2026-04-15 11:46:32
○NSns2.parkingcrew.net2015-08-21 → 2015-12-14 · 4 obs
● 2015-08-21 19:09:52
● 2015-12-14 22:38:06
○ 2016-03-17 06:43:20
○ 2026-04-15 11:46:32
● 2015-12-14 22:38:06
○ 2016-03-17 06:43:20
○ 2026-04-15 11:46:32
○MXmail.h-email.net2015-08-21 → 2015-12-14 · 4 obs
● 2015-08-21 19:09:52
● 2015-12-14 22:38:06
○ 2016-03-17 06:43:20
○ 2026-04-15 11:46:32
● 2015-12-14 22:38:06
○ 2016-03-17 06:43:20
○ 2026-04-15 11:46:32
○A119.81.236.932016-03-17 → 2017-08-22 · 5 obs
○ 2015-12-14 22:38:06
● 2016-03-17 06:43:20
● 2017-08-22 14:42:54
○ 2026-04-08 23:45:52
○ 2026-04-15 11:46:32
● 2016-03-17 06:43:20
● 2017-08-22 14:42:54
○ 2026-04-08 23:45:52
○ 2026-04-15 11:46:32
○A185.53.179.72015-08-21 → 2015-08-21 · 3 obs
● 2015-08-21 19:09:52
○ 2015-12-14 22:38:06
○ 2026-04-15 11:46:32
○ 2015-12-14 22:38:06
○ 2026-04-15 11:46:32
○A54.72.9.512015-12-14 → 2015-12-14 · 4 obs
○ 2015-08-21 19:09:52
● 2015-12-14 22:38:06
○ 2016-03-17 06:43:20
○ 2026-04-15 11:46:32
● 2015-12-14 22:38:06
○ 2016-03-17 06:43:20
○ 2026-04-15 11:46:32
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| in | ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.org, ns10.trs-dns.info | - |
| 533.in | ns2.dyna-ns.net, ns1.dyna-ns.net | - |
✅ Authoritative Response
Server:162.159.25.5
NS records: ns2.dyna-ns.net, ns1.dyna-ns.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for 533.in (unsigned zone)
⏱️ Timing
Total: 219ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
Analysis
Name Servers
Delegation for 533.in rests with two name servers, ns1.dyna-ns.net and ns2.dyna-ns.net.
533.in shares the same name server setup as other domains, including aiandtech.com, mktml.com, sns.im, df21fc770bb68787.com and 137303.com.
Host names with four IP numbers:
ns1.dyna-ns.net points to 2400:cb00:2049:1::a29f:1a5c, 2400:cb00:2049:1::a29f:1b9e, 162.159.26.92 and 162.159.27.158
ns2.dyna-ns.net points to 2400:cb00:2049:1::a29f:1805, 2400:cb00:2049:1::a29f:1905, 162.159.24.5 and 162.159.25.5