singularity-networks.com - dns.ninja
singularity-networks.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.cisco.com ⚠️ Not in zone NS records | ||||||
| A | 2001:420:1101:6::a🇺🇸 ASNTTCISCO2001:420:1100::/41 170 West Tasman Drive San Jose CA 95134 United States | ||||||
| PTR | ns1.cisco.com | ||||||
| A | 72.163.5.201🇺🇸 ASNTTCISCO72.163.0.0/18 170 West Tasman Drive San Jose CA 95134 United States | ||||||
| PTR | ns1.cisco.com | ||||||
| NS | ns2.cisco.com ⚠️ Not in zone NS records | ||||||
| A | 2001:420:2041:5000::a🇺🇸 ASNTTCISCO2001:420:2000::/35 170 West Tasman Drive San Jose CA 95134 United States | ||||||
| PTR | ns2.cisco.com | ||||||
| A | 64.102.255.44🇺🇸 ASNTTCISCO64.102.0.0/16 170 West Tasman Drive San Jose CA 95134 United States | ||||||
| PTR | ns2.cisco.com | ||||||
| NS | ns3.cisco.com ⚠️ Not in zone NS records | ||||||
| A | 2001:420:1201:7::a🇺🇸 ASNTTCISCO2001:420:1200::/41 170 West Tasman Drive San Jose CA 95134 United States | ||||||
| PTR | ns3.cisco.com | ||||||
| A | 173.37.146.41🇺🇸 ASNTTCISCO173.37.128.0/19 170 West Tasman Drive San Jose CA 95134 United States | ||||||
| PTR | ns3.cisco.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=1782600010 | ||||||
Same first word
singularity-networks.com |
singularity-networks.net |
DNS History
14 records (3 active, 11 former)
●NSns1.cisco.com2026-05-03 → 2026-06-27 · 3 obs
○ 2017-06-19 09:50:34
● 2026-05-03 12:24:20
● 2026-06-27 22:45:36
● 2026-05-03 12:24:20
● 2026-06-27 22:45:36
○NSns1.mydyndns.org2015-07-02 → 2017-06-19 · 4 obs
● 2015-07-02 07:37:56
● 2017-06-19 09:50:34
○ 2026-05-03 12:24:20
○ 2026-06-27 22:45:36
● 2017-06-19 09:50:34
○ 2026-05-03 12:24:20
○ 2026-06-27 22:45:36
○NSns1165.dns.dyn.com2015-07-02 → 2017-06-19 · 4 obs
● 2015-07-02 07:37:56
● 2017-06-19 09:50:34
○ 2026-05-03 12:24:20
○ 2026-06-27 22:45:36
● 2017-06-19 09:50:34
○ 2026-05-03 12:24:20
○ 2026-06-27 22:45:36
●NSns2.cisco.com2026-05-03 → 2026-06-27 · 3 obs
○ 2017-06-19 09:50:34
● 2026-05-03 12:24:20
● 2026-06-27 22:45:36
● 2026-05-03 12:24:20
● 2026-06-27 22:45:36
○NSns2181.dns.dyn.com2015-07-02 → 2017-06-19 · 4 obs
● 2015-07-02 07:37:56
● 2017-06-19 09:50:34
○ 2026-05-03 12:24:20
○ 2026-06-27 22:45:36
● 2017-06-19 09:50:34
○ 2026-05-03 12:24:20
○ 2026-06-27 22:45:36
●NSns3.cisco.com2026-05-03 → 2026-06-27 · 3 obs
○ 2017-06-19 09:50:34
● 2026-05-03 12:24:20
● 2026-06-27 22:45:36
● 2026-05-03 12:24:20
● 2026-06-27 22:45:36
○NSns3164.dns.dyn.com2015-07-02 → 2017-06-19 · 4 obs
● 2015-07-02 07:37:56
● 2017-06-19 09:50:34
○ 2026-05-03 12:24:20
○ 2026-06-27 22:45:36
● 2017-06-19 09:50:34
○ 2026-05-03 12:24:20
○ 2026-06-27 22:45:36
○NSns4139.dns.dyn.com2015-07-02 → 2017-06-19 · 4 obs
● 2015-07-02 07:37:56
● 2017-06-19 09:50:34
○ 2026-05-03 12:24:20
○ 2026-06-27 22:45:36
● 2017-06-19 09:50:34
○ 2026-05-03 12:24:20
○ 2026-06-27 22:45:36
○MXalt1.aspmx.l.google.com2015-07-02 → 2017-06-19 · 4 obs
● 2015-07-02 07:37:56
● 2017-06-19 09:50:34
○ 2026-05-03 12:24:20
○ 2026-06-27 22:45:36
● 2017-06-19 09:50:34
○ 2026-05-03 12:24:20
○ 2026-06-27 22:45:36
○MXalt2.aspmx.l.google.com2015-07-02 → 2017-06-19 · 4 obs
● 2015-07-02 07:37:56
● 2017-06-19 09:50:34
○ 2026-05-03 12:24:20
○ 2026-06-27 22:45:36
● 2017-06-19 09:50:34
○ 2026-05-03 12:24:20
○ 2026-06-27 22:45:36
○MXaspmx.l.google.com2015-07-02 → 2017-06-19 · 4 obs
● 2015-07-02 07:37:56
● 2017-06-19 09:50:34
○ 2026-05-03 12:24:20
○ 2026-06-27 22:45:36
● 2017-06-19 09:50:34
○ 2026-05-03 12:24:20
○ 2026-06-27 22:45:36
○A104.155.177.1462017-06-19 → 2017-06-19 · 4 obs
○ 2016-11-25 01:39:16
● 2017-06-19 09:50:34
○ 2026-05-03 12:24:20
○ 2026-06-27 22:45:36
● 2017-06-19 09:50:34
○ 2026-05-03 12:24:20
○ 2026-06-27 22:45:36
○A199.34.228.472015-07-02 → 2016-01-22 · 4 obs
● 2015-07-02 07:37:56
● 2016-01-22 06:00:12
○ 2016-04-11 14:14:52
○ 2026-06-27 22:45:36
● 2016-01-22 06:00:12
○ 2016-04-11 14:14:52
○ 2026-06-27 22:45:36
○A216.146.39.1252016-04-11 → 2016-11-25 · 5 obs
○ 2016-01-22 06:00:12
● 2016-04-11 14:14:52
● 2016-11-25 01:39:16
○ 2017-06-19 09:50:34
○ 2026-06-27 22:45:36
● 2016-04-11 14:14:52
● 2016-11-25 01:39:16
○ 2017-06-19 09:50:34
○ 2026-06-27 22:45:36
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| singularity-networks.com | ns1.cisco.com, ns2.cisco.com, ns3.cisco.com | 6 records |
✅ Authoritative Response
Server:72.163.5.201
NS records: ns1.cisco.com, ns2.cisco.com, ns3.cisco.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for singularity-networks.com (unsigned zone)
⏱️ Timing
Total: 243ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
📌 Glue Records Collected
Total: 6
Out-of-bailiwick: 6 (ns1.cisco.com, ns1.cisco.com, ns2.cisco.com...)
Analysis
Name Servers
singularity-networks.com carries NS records delegating to ns1.cisco.com, ns2.cisco.com and ns3.cisco.com.
At least some of singularity-networks.com's name servers are shared with other domains, for example vsider.com, cisco-nexus.com, 244.135.192.in-addr.arpa and two more.
ns1.cisco.com, ns2.cisco.com and ns3.cisco.com are three hostnames that each resolve to a pair of IP addresses: ns1.cisco.com to 72.163.5.201 and 2001:420:1101:6::a, ns2.cisco.com to 64.102.255.44 and 2001:420:2041:5000::a, and ns3.cisco.com to 173.37.146.41 and 2001:420:1201:7::a.