cloud-bridging.com - dns.ninja
cloud-bridging.com
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=1785490437 | ||||||
Same first word
cloud-bridging.com |
DNS History
10 records (8 active, 2 former)
●NSens1.net-chinese.com.tw2017-01-04 → 2026-07-31 · 2 obs
● 2026-07-31 09:39:26
●NSens2.net-chinese.com.tw2017-01-04 → 2026-07-31 · 2 obs
● 2026-07-31 09:39:26
●MXalt1.aspmx.l.google.com2017-01-04 → 2026-07-31 · 2 obs
● 2026-07-31 09:39:26
●MXalt2.aspmx.l.google.com2017-01-04 → 2026-07-31 · 2 obs
● 2026-07-31 09:39:26
●MXalt3.aspmx.l.google.com2017-01-04 → 2026-07-31 · 2 obs
● 2026-07-31 09:39:26
●MXalt4.aspmx.l.google.com2017-01-04 → 2026-07-31 · 2 obs
● 2026-07-31 09:39:26
●MXaspmx.l.google.com2017-01-04 → 2026-07-31 · 2 obs
● 2026-07-31 09:39:26
●A1.34.162.812026-07-31 → 2026-07-31 · 2 obs
● 2026-07-31 09:39:26
○A104.199.189.942017-01-04 → 2017-01-04 · 3 obs
○ 2017-12-21 19:31:02
○ 2026-07-31 09:39:26
○A114.34.5.1112017-12-21 → 2017-12-21 · 3 obs
● 2017-12-21 19:31:02
○ 2026-07-31 09:39:26
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | m.gtld-servers.net, k.gtld-servers.net, f.gtld-servers.net, b.gtld-servers.net... | - |
| cloud-bridging.com | ens1.net-chinese.com.tw, ens2.net-chinese.com.tw | - |
✅ Authoritative Response
Server:104.199.131.53
NS records: ens1.net-chinese.com.tw, ens2.net-chinese.com.tw
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for cloud-bridging.com (unsigned zone)
⏱️ Timing
Total: 809ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 1.34.162.81 |
| NS | 2 | ens2.net-chinese.com.tw, ens1.net-chinese.com.tw |
| MX | 5 | alt1.aspmx.l.google.com (pri: 3), alt3.aspmx.l.google.com (pri: 7)... |
| TXT | 1 | MS=A8F70460D58EA2783682F8956424326E62545 |
| SOA | 1 | ens1.net-chinese.com.tw abuse.digiage.co |
Analysis
IP Addresses
cloud-bridging.com points to a single IP number: 1.34.162.81.
Host names like 1-34-162-81.hinet-ip.hinet.net are further examples that share IP numbers with cloud-bridging.com.
Name Servers
Two name servers handle the delegation for cloud-bridging.com: ens1.net-chinese.com.tw and ens2.net-chinese.com.tw.
cloud-bridging.com shares its name server setup with other domains, including unitelgroups.com, physi3.com, oeiltd.com and two others.
Each of ens1.net-chinese.com.tw and ens2.net-chinese.com.tw has one IP address: ens1.net-chinese.com.tw uses 104.199.131.53 and ens2.net-chinese.com.tw uses 104.199.229.182.
Mail Servers
cloud-bridging.com has five mail servers, which are aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
cloud-bridging.com shares mail servers — at least in part — with other domains, including pqc.vn, e-logix.us, ns500758.ns500758.ns500758.ns500735.ns500735.ns500736.ns500698.ns500735.ns500698.ns500736.ns500698.ns500619.ns500652.ns500576.trackreceptor.com and two others.
These mail servers are frequently paired with the mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com.
Host names with two IP numbers:
aspmx.l.google.com resolves to two addresses: 172.253.63.27 and 2607:f8b0:4004:c17::1a.
alt1.aspmx.l.google.com resolves to two addresses: 108.177.123.27 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com resolves to two addresses: 74.125.193.27 and 2a00:1450:400b:c01::1b.
alt3.aspmx.l.google.com resolves to two addresses: 192.178.223.27 and 2a00:1450:4009:c0f::1a.
alt4.aspmx.l.google.com resolves to two addresses: 172.253.157.26 and 2a00:1450:400c:c23::1b.