ns1.cloudsingularity.com - robtex.com
ns1.cloudsingularity.com
| DNSSEC | β οΈ Not signed | ||||||
| A | 2600:180a:1001::1πΊπΈ Tiggee | ||||||
| PTR | ns11.constellix.com | ||||||
| A | 96.45.80.1πΊπΈ Tiggee | ||||||
cloudsingularity.com
| DNSSEC | β οΈ Not signed | ||||||
| NS | ns1.cloudsingularity.com β | ||||||
| NS | ns2.cloudsingularity.com | ||||||
| NS | ns3.cloudsingularity.com | ||||||
| NS | ns4.cloudsingularity.com | ||||||
| NS | ns5.cloudsingularity.com | ||||||
| NS | ns6.cloudsingularity.com | ||||||
| SOA | ns1.cloudsingularity.comdns-admin@cloudsingularity.net 2015-01-01 #12 | ||||||
NS for
Same first word
Similar names
DNS History
2 records (2 active, 0 former)
βA2600:180a:1001::12026-02-14 β 2026-02-24 Β· 2 obs
β 2026-02-24 09:16:10
βA96.45.80.12026-02-14 β 2026-02-24 Β· 2 obs
β 2026-02-24 09:16:10
π DNS Trace
π Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| cloudsingularity.com | ns6.cloudsingularity.com, ns5.cloudsingularity.com, ns4.cloudsingularity.com, ns3.cloudsingularity.com... | - |
β Authoritative Response
Server: 43.247.170.1
NS records: ns6.cloudsingularity.com, ns5.cloudsingularity.com, ns4.cloudsingularity.com, ns3.cloudsingularity.com, ns2.cloudsingularity.com, ns1.cloudsingularity.com
π DNSSEC Status
β οΈ Insecure (no DNSSEC)
No DS record for cloudsingularity.com (unsigned zone)
β±οΈ Timing
Total: 66ms | Queries: -
π Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 96.45.80.1 |
| AAAA | 1 | 2600:180a:1001::1 |
AI analysis
For cloudsingularity.com, ns1.cloudsingularity.com is used as its name server.
ns2.cloudsingularity.com, ns3.cloudsingularity.com and ns4.cloudsingularity.com are commonly used as name servers together with ns1.cloudsingularity.com.
ns1.cloudsingularity.com points to two IP numbers: 2600:180a:1001::1 and 96.45.80.1.
Other host names such as ns1.tipgroup.be, ns1.e2services.net, sg2.naga.tel, ns1.fmcc.edu and ns0.babybuds.com.au share IPs with ns1.cloudsingularity.com.