singularitynet.com - dns.ninja
singularitynet.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=1782925146 | ||||||
Same first word
singularitynet.com |
singularitynet.io |
Similar names
DNS History
12 records (11 active, 1 former)
●NSns1.name.com2026-02-20 → 2026-07-01 · 3 obs
● 2026-02-20 05:48:32
● 2026-07-01 17:24:22
●MXalt1.aspmx.l.google.com2016-05-09 → 2026-07-01 · 2 obs
● 2026-07-01 17:24:22
●MXalt2.aspmx.l.google.com2016-05-09 → 2026-07-01 · 2 obs
● 2026-07-01 17:24:22
●MXaspmx.l.google.com2016-05-09 → 2026-07-01 · 2 obs
● 2026-07-01 17:24:22
●MXaspmx2.googlemail.com2016-05-09 → 2026-07-01 · 2 obs
● 2026-07-01 17:24:22
●MXaspmx3.googlemail.com2016-05-09 → 2026-07-01 · 2 obs
● 2026-07-01 17:24:22
●A75.126.100.202015-11-09 → 2026-07-01 · 5 obs
○ 2016-02-12 08:24:40
○ 2016-05-09 04:52:54
● 2017-01-17 09:40:52
● 2026-07-01 17:24:22
○A75.126.101.2412016-02-12 → 2016-05-09 · 5 obs
● 2016-02-12 08:24:40
● 2016-05-09 04:52:54
○ 2017-01-17 09:40:52
○ 2026-07-01 17:24:22
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net... | - |
| singularitynet.com | ns1bcp.name.com, ns2fjz.name.com, ns3qty.name.com, ns4hmp.name.com | 8 records |
✅ Authoritative Response
Server:163.114.216.17
NS records: ns1bcp.name.com, ns2fjz.name.com, ns3qty.name.com, ns4hmp.name.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for singularitynet.com (unsigned zone)
⏱️ Timing
Total: 679ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 75.126.100.20 |
| NS | 4 | ns1bcp.name.com, ns2fjz.name.com... |
| MX | 5 | alt1.aspmx.l.google.com (pri: 20), alt2.aspmx.l.google.com (pri: 30)... |
| TXT | 1 | google-site-verification=CTLJTFQQMZH-0-u |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns1bcp.name.com, ns1bcp.name.com, ns2fjz.name.com...)
Analysis
IP Addresses
singularitynet.com has exactly one IP address — 75.126.100.20.
ruysantos.com, gurocak.com, emandwitdesign.com plus two other host names have IP numbers in common with singularitynet.com.
Name Servers
Five name servers handle delegation for singularitynet.com: ns1.name.com, ns1bcp.name.com, ns2fjz.name.com and two others.
singularitynet.com has at least partial name server overlap with other domains, such as intra-systeme.com, bestofnerd.com, 3jg99g30.com and two others.
ns4hmp.name.com, ns3qty.name.com and ns3gmt.name.com — plus 7 other name servers — are commonly paired with these name servers.
Host names pointing 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.
ns2fjz.name.com directs traffic to 163.114.216.49 and 2402:cf80:107::1.
ns3qty.name.com directs traffic to 163.114.217.17 and 2a00:edc0:107::49.
ns4hmp.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
singularitynet.com is handled by five mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
At least some of the mail servers used by singularitynet.com are shared with other domains: ns500671.ns500671.ns500742.ns500671.ns500754.ns500704.ns500731.ns500291.ns500649.ns500291.ns500291.ns500291.ns500131.lustychickser.com, ns500698.ns500698.ns500698.ns500735.ns500736.ns500735.ns500698.ns500735.ns500576.ns500698.ns500619.ns500698.ns500652.ns500576.trackreceptor.com, ns500765.ns500734.ns500734.ns500734.ns500693.ns500693.ns500699.ns500699.ns500699.ns500699.ns500588.ns500588.ns500588.ns500699.ns500632.ns500632.ns500612.ns500110.dtrkdll.com and two others among them.
These mail servers are often deployed together with alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 other mail servers.
Host names pointing to two IP addresses:
aspmx2.googlemail.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1a.
aspmx3.googlemail.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1b.
aspmx.l.google.com directs traffic to 172.253.115.27 and 2607:f8b0:4004:c29::1b.
alt1.aspmx.l.google.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1a.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 108.177.123.26 IP addresses each.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 172.253.116.26 IP addresses each.