bitforge.cloud - dns.ninja
bitforge.cloud
cloud
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns01.trs-dns.com ⭐ | ||||||
| NS | ns.trs-dns.com | ||||||
| NS | ns01.trs-dns.net | ||||||
| NS | ns10.trs-dns.info | ||||||
| NS | ns10.trs-dns.org | ||||||
| SOA | ns.trs-dns.comtrs-ops@tucows.com serial=1782453929 | ||||||
PTR for
Same first word
bitforge.tech |
bitforge.us |
bitforge.it |
bitforge.com |
bitforge.org |
bitforge.de |
bitforge.s3.amazonaws.com |
bitforge.top |
bitforge.net |
bitforge.com.my |
bitforge.cloud |
bitforge.com.br |
bitforge.ch |
bitforge.biz |
bitforge.icu |
Similar names
DNS History
13 records (11 active, 2 former)
○NSlara.ns.cloudflare.com2017-03-16 → 2017-03-16 · 3 obs
○ 2020-01-30 10:33:28
○ 2026-06-26 06:27:06
●NSns1.name.com2026-03-19 → 2026-06-26 · 3 obs
● 2026-03-19 00:45:10
● 2026-06-26 06:27:06
●NSns1bcp.name.com2026-03-19 → 2026-06-26 · 3 obs
● 2026-03-19 00:45:10
● 2026-06-26 06:27:06
●NSns2dfg.name.com2026-03-19 → 2026-06-26 · 3 obs
● 2026-03-19 00:45:10
● 2026-06-26 06:27:06
●NSns3cjl.name.com2026-03-19 → 2026-06-26 · 3 obs
● 2026-03-19 00:45:10
● 2026-06-26 06:27:06
●NSns4clq.name.com2026-03-19 → 2026-06-26 · 3 obs
● 2026-03-19 00:45:10
● 2026-06-26 06:27:06
○NSrob.ns.cloudflare.com2017-03-16 → 2017-03-16 · 3 obs
○ 2020-01-30 10:33:28
○ 2026-06-26 06:27:06
●MXalt1.aspmx.l.google.com2026-03-19 → 2026-06-26 · 2 obs
● 2026-06-26 06:27:06
●MXalt2.aspmx.l.google.com2026-03-19 → 2026-06-26 · 2 obs
● 2026-06-26 06:27:06
●MXalt3.aspmx.l.google.com2026-03-19 → 2026-06-26 · 2 obs
● 2026-06-26 06:27:06
●MXalt4.aspmx.l.google.com2026-03-19 → 2026-06-26 · 2 obs
● 2026-06-26 06:27:06
●MXaspmx.l.google.com2026-03-19 → 2026-06-26 · 2 obs
● 2026-06-26 06:27:06
●A31.172.77.2462026-03-19 → 2026-06-26 · 2 obs
● 2026-06-26 06:27:06
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| cloud | ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.org, ns10.trs-dns.info | - |
| bitforge.cloud | ns1bcp.name.com, ns2dfg.name.com, ns3cjl.name.com, ns4clq.name.com | - |
✅ Authoritative Response
Server:163.114.217.49
NS records: ns1bcp.name.com, ns2dfg.name.com, ns3cjl.name.com, ns4clq.name.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for bitforge.cloud (unsigned zone)
⏱️ Timing
Total: 873ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 31.172.77.246 |
| NS | 4 | ns1bcp.name.com, ns2dfg.name.com... |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| TXT | 2 | google-site-verification=GECjZNnvCKvA-r3, google-site-verification=kjlqZlnfTR_SYF4 |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
Analysis
IP Addresses
bitforge.cloud resolves to one IP address: 31.172.77.246.
flutterize.com, for instance, is one of the other host names sharing IP numbers with bitforge.cloud.
Name Servers
bitforge.cloud has five name servers, which are ns1.name.com, ns1bcp.name.com, ns2dfg.name.com and two others.
bitforge.cloud partially shares its NS delegation with several other domains, including cicali.org, itherald.com, carpia.com and two others.
In DNS configurations, these name servers often share authority with ns4clq.name.com, ns3cjl.name.com, ns1cnb.name.com and 7 other name servers.
Hostnames that resolve to two IP addresses:
ns1.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns1bcp.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns2dfg.name.com directs traffic to 163.114.216.49 and 2402:cf80:107::1.
ns3cjl.name.com directs traffic to 163.114.217.17 and 2a00:edc0:107::49.
ns4clq.name.com directs traffic to 163.114.217.49 and 2402:cf80:107::49.
Both ns1.name.com and ns1bcp.name.com resolve to 2a00:edc0:107::1 IP addresses each.
Both ns1.name.com and ns1bcp.name.com resolve to 163.114.216.17 IP addresses each.
Mail Servers
bitforge.cloud is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
bitforge.cloud has at least partial mail server overlap with other domains such as ns500742.ns500742.ns500742.ns500754.ns500688.ns500705.ns500688.ns500704.ns500704.ns500688.ns500649.ns500131.lustychickser.com, ns500759.ns500759.ns500758.ns500735.ns500736.ns500736.ns500736.ns500735.ns500698.ns500708.ns500619.ns500576.ns500652.trackreceptor.com, providencechurch.com.au and two more.
The mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com are commonly seen alongside these mail servers.
Hostnames that resolve to two IP addresses:
aspmx.l.google.com directs traffic to 74.125.137.27 and 2607:f8b0:4023:c03::1a.
alt1.aspmx.l.google.com directs traffic to 142.250.102.26 and 2a00:1450:4025:402::1a.
alt2.aspmx.l.google.com directs traffic to 172.253.145.27 and 2607:f8b0:4023:3003::1a.
alt3.aspmx.l.google.com directs traffic to 142.251.127.26 and 2a00:1450:4001:c21::1b.
alt4.aspmx.l.google.com directs traffic to 172.253.157.26 and 2a00:1450:400c:c23::1b.