comunity-crypto.id - robtex.com
comunity-crypto.id
| DNSSEC | ⚠️ Not signed | ||||||
| A | 103.131.51.116🇮🇩 IDNIC-JALANET-AS-ID103.131.51.0/24 Proxy-registered route object | ||||||
| NS | ns1.hoster.co.id ⭐ | ||||||
| A | 192.210.214.149🇺🇸 Colocrossing-AS192.210.214.0/24 ColoCrossing-Colo4 | ||||||
| PTR | 192-210-214-149-host.colocrossing.com | ||||||
| NS | ns2.hoster.co.id | ||||||
| A | 103.131.51.220🇮🇩 IDNIC-JALANET-AS-ID103.131.51.0/24 Proxy-registered route object | ||||||
| PTR | host.131.51.220.colo.co.id | ||||||
| NS | ns3.hoster.co.id | ||||||
| A | 23.94.36.29🇺🇸 Colocrossing-AS23.94.36.0/23 ColoCrossing | ||||||
| PTR | 23-94-36-29-host.colocrossing.com | ||||||
| NS | ns4.hoster.co.id | ||||||
| A | 103.131.51.209🇮🇩 IDNIC-JALANET-AS-ID103.131.51.0/24 Proxy-registered route object | ||||||
| MX | comunity-crypto.id ⭐ | ||||||
| A | 103.131.51.116🇮🇩 IDNIC-JALANET-AS-ID103.131.51.0/24 Proxy-registered route object | ||||||
| TXT | v=spf1 +a +mx +ip4:103.16.198.13 +ip4:103.131.51.46 +ip4:103.131.51.116 +ip4:... | ||||||
| SOA | ns1.hoster.co.idbonechruser@hosterserver.com 2026-05-28 #1 | ||||||
id
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | b.dns.id ⭐ | ||||||
| NS | c.dns.id | ||||||
| NS | d.dns.id | ||||||
| NS | e.dns.id | ||||||
| NS | ns4.apnic.net ⚠️ Not in parent delegation | ||||||
| SOA | b.dns.idhostmaster@pandi.id serial=2026178297 | ||||||
MX for
comunity-crypto.id |
Same first word
comunity-crypto.id |
DNS History
6 records (6 active, 0 former)
●NSns1.hoster.co.id2026-03-29 → 2026-07-14 · 2 obs
● 2026-07-14 00:49:04
●NSns2.hoster.co.id2026-03-29 → 2026-07-14 · 2 obs
● 2026-07-14 00:49:04
●NSns3.hoster.co.id2026-03-29 → 2026-07-14 · 2 obs
● 2026-07-14 00:49:04
●NSns4.hoster.co.id2026-03-29 → 2026-07-14 · 2 obs
● 2026-07-14 00:49:04
●MXcomunity-crypto.id2026-03-29 → 2026-07-14 · 2 obs
● 2026-07-14 00:49:04
●A103.131.51.1162026-03-29 → 2026-07-14 · 2 obs
● 2026-07-14 00:49:04
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| id | b.dns.id, c.dns.id, d.dns.id, e.dns.id | - |
| comunity-crypto.id | ns2.hoster.co.id, ns3.hoster.co.id, ns4.hoster.co.id, ns1.hoster.co.id | - |
✅ Authoritative Response
Server:103.131.51.220
NS records: ns2.hoster.co.id, ns3.hoster.co.id, ns4.hoster.co.id, ns1.hoster.co.id
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for comunity-crypto.id (unsigned zone)
⏱️ Timing
Total: 1130ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 103.131.51.116 |
| NS | 4 | ns4.hoster.co.id, ns3.hoster.co.id... |
| MX | 1 | comunity-crypto.id (pri: 0) |
| TXT | 1 | v=spf1 +a +mx +ip4:103.16.198.13 +ip4:10 |
| SOA | 1 | ns1.hoster.co.id bonechruser.hosterserve |
Analysis
Mail Server Role
comunity-crypto.id handles its own mail, functioning as its own mail server.
IP Addresses
comunity-crypto.id resolves to just one IP address, 103.131.51.116.
Two other host names, along with pmb.teknik.uniga.ac.id.fteknikuniga.ac.id, www.fteknik.uniga.ac.id.fteknikuniga.ac.id and gapuratour.co.id, also share IP numbers with comunity-crypto.id.
Name Servers
The NS records for comunity-crypto.id point to four name servers: ns1.hoster.co.id, ns2.hoster.co.id, ns3.hoster.co.id and ns4.hoster.co.id.
There is at least partial name server overlap between comunity-crypto.id and other domains — viactiontype.net, bytheglassshow.com, andil.id and two more among them.
The hosts ns1.hoster.co.id, ns2.hoster.co.id, ns3.hoster.co.id and ns4.hoster.co.id all resolve to exactly one IP address each: 192.210.214.149, 103.131.51.220, 23.94.36.29 and 103.131.51.209 respectively.
Mail Servers
comunity-crypto.id is served by just one mail server: comunity-crypto.id.
comunity-crypto.id carries a single IP number, which is 103.131.51.116.