connectedprocess.com - dns.ninja
connectedprocess.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 64.99.64.37🇨🇦 TUCOWS64.99.0.0/16 Tucows.com Co | ||||||
| PTR | osrs.systemdns.com | ||||||
| NS | ns1.systemdns.com ⭐ | ||||||
| A | 2604:4000:0:d:216:40:47:90🇨🇦 TUCOWS2604:4000::/48 -BRA-IPV6-BLK1.1/NET-2604:4000 | ||||||
| PTR | ns1.systemdns.com | ||||||
| A | 216.40.47.90🇨🇦 TUCOWS216.40.47.0/24 -BRA-BLK1.4/NET-216-40-47-0 | ||||||
| PTR | ns1.systemdns.com | ||||||
| NS | ns2.systemdns.com | ||||||
| A | 2604:4000:2800:d:64:99:148:16🇨🇦 TUCOWS-32604:4000:2800::/37 Tucows.com Co. | ||||||
| PTR | ns2.systemdns.com | ||||||
| A | 64.98.148.16🇨🇦 TUCOWS-364.98.144.0/20 Tucows.com Co. | ||||||
| PTR | ns2.systemdns.com | ||||||
| NS | ns3.systemdns.com | ||||||
| A | 2604:4000:0:d:64:99:96:36🇨🇦 TUCOWS2604:4000::/48 -BRA-IPV6-BLK1.1/NET-2604:4000 | ||||||
| PTR | ns3.systemdns.com | ||||||
| A | 64.99.96.36🇨🇦 TUCOWS64.99.96.0/24 -BRA-BLK2.7.2 | ||||||
| PTR | ns3.systemdns.com | ||||||
| SOA | ns1.systemdns.comhostmaster@systemdns.com serial=1752189302 | ||||||
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=1790364854 | ||||||
Same first word
connectedprocess.info |
connectedprocess.com |
Similar names
Previous names
Next names
DNS History
8 records (4 active, 4 former)
○NSns1.dragonfli.ca2015-06-11 → 2017-04-07 · 4 obs
● 2017-04-07 01:29:54
○ 2026-09-16 01:39:26
○ 2026-09-25 19:48:10
●NSns1.systemdns.com2026-09-16 → 2026-09-25 · 3 obs
● 2026-09-16 01:39:26
● 2026-09-25 19:48:10
○NSns2.dragonfli.ca2015-06-11 → 2017-04-07 · 4 obs
● 2017-04-07 01:29:54
○ 2026-09-16 01:39:26
○ 2026-09-25 19:48:10
●NSns2.systemdns.com2026-09-16 → 2026-09-25 · 3 obs
● 2026-09-16 01:39:26
● 2026-09-25 19:48:10
●NSns3.systemdns.com2026-09-16 → 2026-09-25 · 3 obs
● 2026-09-16 01:39:26
● 2026-09-25 19:48:10
○MXmx.connectedprocess.com.cust.a.hostedemail.com2015-06-11 → 2017-04-07 · 4 obs
● 2017-04-07 01:29:54
○ 2026-09-16 01:39:26
○ 2026-09-25 19:48:10
●A64.99.64.372026-09-16 → 2026-09-25 · 3 obs
● 2026-09-16 01:39:26
● 2026-09-25 19:48:10
○A74.207.251.122015-06-11 → 2017-04-07 · 4 obs
● 2017-04-07 01:29:54
○ 2026-09-16 01:39:26
○ 2026-09-25 19:48:10
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net... | - |
| connectedprocess.com | ns1.systemdns.com, ns2.systemdns.com, ns3.systemdns.com | 6 records |
✅ Authoritative Response
Server:216.40.47.90
NS records: ns1.systemdns.com, ns2.systemdns.com, ns3.systemdns.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for connectedprocess.com (unsigned zone)
⏱️ Timing
Total: 306ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 64.99.64.37 |
| NS | 3 | ns3.systemdns.com, ns1.systemdns.com... |
| SOA | 1 | ns1.systemdns.com hostmaster.systemdns.c |
📌 Glue Records Collected
Total: 6
Out-of-bailiwick: 6 (ns1.systemdns.com, ns1.systemdns.com, ns2.systemdns.com...)
Analysis
IP Addresses
connectedprocess.com resolves to one IP address: 64.99.64.37.
tukyoot.com, alexandertechniqueforyou.com, signaturesanding.com.au and two other host names share IP numbers with connectedprocess.com.
Name Servers
Three name servers are authoritative for connectedprocess.com: ns1.systemdns.com, ns2.systemdns.com and ns3.systemdns.com.
At least some of connectedprocess.com's name servers are shared with other domains, for example allproplumbingofbrevard.com, polarissrx.com, business-employee-insurance.com and two more.
ns1.systemdns.com resolves to 216.40.47.90 and 2604:4000:0:d:216:40:47:90. ns2.systemdns.com resolves to 64.98.148.16 and 2604:4000:2800:d:64:99:148:16. ns3.systemdns.com resolves to 64.99.96.36 and 2604:4000:0:d:64:99:96:36. All three hostnames point to two IP numbers each.