playdb.id - robtex.com
playdb.id
| DNSSEC | ⚠️ Not signed | ||||||
| A | 157.20.35.141IDNIC-ERA-AS-ID157.20.35.0/24 Customer Route | ||||||
| PTR | ip141.35.20-pm2-eradata.id | ||||||
| NS | ns1.eradata.id ⭐ | ||||||
| A | 157.20.35.129IDNIC-ERA-AS-ID157.20.35.0/24 Customer Route | ||||||
| NS | ns2.eradata.id | ||||||
| A | 157.20.35.130IDNIC-ERA-AS-ID157.20.35.0/24 Customer Route | ||||||
| MX | mx1.eradata.id ⭐ | ||||||
| A | 157.20.35.200IDNIC-ERA-AS-ID157.20.35.0/24 Customer Route | ||||||
| MX | mx2.eradata.id(10) | ||||||
| A | 157.20.35.201IDNIC-ERA-AS-ID157.20.35.0/24 Customer Route | ||||||
| TXT | atlassian-domain-verification=vrHcCYc6haYaHISXyrNWRB9hiXcDpZPbHGsD5PRmEskYtNC... | ||||||
| TXT | google-site-verification=g_yyxA4e3kYwVKjYxru4lfz0SXQ_kZvXT42RD0YwW-8 | ||||||
| SOA | ns1.eradata.idadmin@eradata.id 2025-07-10 #71 | ||||||
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 | ||||||
| SOA | b.dns.idhostmaster@pandi.id serial=2026193855 | ||||||
Same first word
Similar names
dbplay.com |
bldpay.com |
byadlp.com |
dbplay.pl |
bdplay.com |
dbplay.netlify.app |
dbplay.xyz |
playbd.com |
pybald.com |
dbplay.it |
pblady.com |
bdplay.cn |
playbd.games |
DNS History
5 records (5 active, 0 former)
●NSns1.eradata.id2026-06-10 → 2026-07-19 · 2 obs
● 2026-07-19 19:59:34
●NSns2.eradata.id2026-06-10 → 2026-07-19 · 2 obs
● 2026-07-19 19:59:34
●MXmx1.eradata.id2026-06-10 → 2026-07-19 · 2 obs
● 2026-07-19 19:59:34
●MXmx2.eradata.id2026-06-10 → 2026-07-19 · 2 obs
● 2026-07-19 19:59:34
●A157.20.35.1412026-06-10 → 2026-07-19 · 2 obs
● 2026-07-19 19:59:34
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| id | b.dns.id, c.dns.id, d.dns.id, e.dns.id | - |
| playdb.id | ns1.eradata.id, ns2.eradata.id | 2 records |
✅ Authoritative Response
Server:157.20.35.129
NS records: ns1.eradata.id, ns2.eradata.id
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for playdb.id (unsigned zone)
⏱️ Timing
Total: 1025ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 157.20.35.141 |
| NS | 2 | ns2.eradata.id, ns1.eradata.id |
| MX | 2 | mx1.eradata.id (pri: 0), mx2.eradata.id (pri: 10) |
| TXT | 2 | atlassian-domain-verification=vrHcCYc6ha, google-site-verification=g_yyxA4e3kYwVKj |
| SOA | 1 | ns1.eradata.id admin.eradata.id |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.eradata.id, ns2.eradata.id)
Analysis
IP Addresses
playdb.id resolves to one IP address: 157.20.35.141.
eranet.id and eradata.id are among other host names that share IP numbers with playdb.id.
Name Servers
playdb.id has two authoritative name servers — ns1.eradata.id and ns2.eradata.id.
playdb.id and eradata.id are among domains that share the same name servers.
The name servers for playdb.id overlap at least partially with those of other domains — for example umt.ac.id.
These name servers commonly appear in combination with the name servers ns1.servhost.id.
Both ns1.eradata.id and ns2.eradata.id have a single IP address each — ns1.eradata.id resolves to 157.20.35.129 while ns2.eradata.id resolves to 157.20.35.130.
Mail Servers
Mail for playdb.id is handled by two mail servers — mx1.eradata.id and mx2.eradata.id.
The mail server configuration of playdb.id is identical to that of other domains — eradata.id being one example.
Both mx1.eradata.id and mx2.eradata.id have a single IP address each — mx1.eradata.id resolves to 157.20.35.200 while mx2.eradata.id resolves to 157.20.35.201.