bcsstudio.com - dns.ninja
bcsstudio.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 3.215.100.79🇺🇸 Amazon3.208.0.0/12 EC2 IAD prefix | ||||||
| PTR | ec2-3-215-100-79.compute-1.amazonaws.com | ||||||
| A | 3.234.189.133🇺🇸 Amazon3.224.0.0/12 EC2 IAD prefix | ||||||
| NS | ns1.cargo.site ⭐ | ||||||
| A | 44.205.91.121🇺🇸 Amazon44.192.0.0/11 EC2 IAD prefix | ||||||
| PTR | ns1.cargo.site | ||||||
| NS | ns2.cargo.site | ||||||
| A | 100.21.27.241🇺🇸 Amazon100.20.0.0/14 EC2 PDX prefix | ||||||
| PTR | ns2.cargo.site | ||||||
| TXT | cargo-domain=purchased | ||||||
| SOA | ns1.cargo.sitehostmaster@bcsstudio.com 2022-11-14 #4 | ||||||
com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1785083872 | ||||||
Same first word
bcsstudio.com |
Similar names
DNS History
13 records (4 active, 9 former)
●NSns1.cargo.site2026-04-09 → 2026-07-26 · 3 obs
● 2026-04-09 13:17:42
● 2026-07-26 17:07:02
○NSns1.filnet.es2015-07-11 → 2017-09-07 · 4 obs
● 2017-09-07 11:11:32
○ 2026-04-09 13:17:42
○ 2026-07-26 17:07:02
●NSns2.cargo.site2026-04-09 → 2026-07-26 · 3 obs
● 2026-04-09 13:17:42
● 2026-07-26 17:07:02
○NSns2.filnet.es2015-07-11 → 2017-09-07 · 4 obs
● 2017-09-07 11:11:32
○ 2026-04-09 13:17:42
○ 2026-07-26 17:07:02
○MXmx1.filnet.es2015-07-11 → 2017-09-07 · 4 obs
● 2017-09-07 11:11:32
○ 2026-04-09 13:17:42
○ 2026-07-26 17:07:02
○MXmx2.filnet.es2015-07-11 → 2017-09-07 · 4 obs
● 2017-09-07 11:11:32
○ 2026-04-09 13:17:42
○ 2026-07-26 17:07:02
○MXmx3.filnet.es2015-07-11 → 2017-09-07 · 4 obs
● 2017-09-07 11:11:32
○ 2026-04-09 13:17:42
○ 2026-07-26 17:07:02
○MXmx4.filnet.es2015-07-11 → 2017-09-07 · 4 obs
● 2017-09-07 11:11:32
○ 2026-04-09 13:17:42
○ 2026-07-26 17:07:02
○MXmx5.filnet.es2015-07-11 → 2017-09-07 · 4 obs
● 2017-09-07 11:11:32
○ 2026-04-09 13:17:42
○ 2026-07-26 17:07:02
○MXmx6.filnet.es2015-07-11 → 2017-09-07 · 4 obs
● 2017-09-07 11:11:32
○ 2026-04-09 13:17:42
○ 2026-07-26 17:07:02
○A217.149.3.712015-07-11 → 2017-09-07 · 4 obs
● 2017-09-07 11:11:32
○ 2026-04-09 13:17:42
○ 2026-07-26 17:07:02
●A3.215.100.792026-04-09 → 2026-07-26 · 3 obs
● 2026-04-09 13:17:42
● 2026-07-26 17:07:02
●A3.234.189.1332026-04-09 → 2026-07-26 · 3 obs
● 2026-04-09 13:17:42
● 2026-07-26 17:07:02
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | d.gtld-servers.net, l.gtld-servers.net, f.gtld-servers.net, i.gtld-servers.net... | - |
| bcsstudio.com | ns1.cargo.site, ns2.cargo.site | - |
✅ Authoritative Response
Server:100.21.27.241
NS records: ns1.cargo.site, ns2.cargo.site
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for bcsstudio.com (unsigned zone)
⏱️ Timing
Total: 433ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 3.234.189.133, 3.215.100.79 |
| NS | 2 | ns1.cargo.site, ns2.cargo.site |
| TXT | 1 | cargo-domain=purchased |
| SOA | 1 | ns1.cargo.site hostmaster.bcsstudio.com |
Analysis
IP Addresses
bcsstudio.com directs to two IP numbers, 3.215.100.79 and 3.234.189.133
Additional host names — anubhagupta.com, liseraven.com, www.alvvays.com and two others — share IP numbers with bcsstudio.com.
Name Servers
bcsstudio.com is served by two delegated name servers, ns1.cargo.site and ns2.cargo.site.
bcsstudio.com shares its name server setup with other domains, including tjgdesign.net, gnybek.com, jenspeedandrews.com and two others.
bcsstudio.com has at least partial name server overlap with other domains, such as labrador.se, eavparquelage.org.br, bdds.mx and two others.
It is common to find these name servers paired with the name servers ns1.cargocollective.com, ns2.cargocollective.com, a.misconfigured.dns.server.invalid and ns3.cargo.site.
ns1.cargo.site directs to 44.205.91.121 and ns2.cargo.site directs to 100.21.27.241; each host name points to exactly one IP number.