cloud-process.com - dns.ninja
cloud-process.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=1790283749 | ||||||
Same first word
cloud-process.com |
Similar names
Previous names
Next names
DNS History
9 records (8 active, 1 former)
βNSns1.netnames.net2015-05-12 β 2026-09-24 Β· 2 obs
β 2026-09-24 21:29:28
βNSns2.netnames.net2015-05-12 β 2026-09-24 Β· 2 obs
β 2026-09-24 21:29:28
βNSns5.netnames.net2015-05-12 β 2026-09-24 Β· 2 obs
β 2026-09-24 21:29:28
βNSns6.netnames.net2015-05-12 β 2026-09-24 Β· 2 obs
β 2026-09-24 21:29:28
βMXrelay1.netnames.net2015-05-12 β 2026-09-24 Β· 2 obs
β 2026-09-24 21:29:28
βMXrelay2.netnames.net2015-05-12 β 2026-09-24 Β· 2 obs
β 2026-09-24 21:29:28
βA165.160.13.202020-03-05 β 2026-09-24 Β· 3 obs
β 2020-03-05 23:40:58
β 2026-09-24 21:29:28
βA165.160.15.202020-03-05 β 2026-09-24 Β· 3 obs
β 2020-03-05 23:40:58
β 2026-09-24 21:29:28
βA185.26.230.1292015-05-12 β 2017-04-13 Β· 4 obs
β 2017-04-13 16:20:06
β 2020-03-05 23:40:58
β 2026-09-24 21:29:28
π DNS Trace
π Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | k.gtld-servers.net, h.gtld-servers.net, m.gtld-servers.net, l.gtld-servers.net... | - |
| cloud-process.com | ns2.netnames.net, ns1.netnames.net, ns5.netnames.net, ns6.netnames.net | - |
β Authoritative Response
Server:156.154.131.100
NS records: ns2.netnames.net, ns1.netnames.net, ns5.netnames.net, ns6.netnames.net
π DNSSEC Status
β οΈ Insecure (no DNSSEC)
No DS record for cloud-process.com (unsigned zone)
β±οΈ Timing
Total: 922ms | Queries: -
π Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 165.160.13.20, 165.160.15.20 |
| NS | 4 | ns1.netnames.net, ns2.netnames.net... |
| MX | 2 | relay1.netnames.net (pri: 10), relay2.netnames.net (pri: 20) |
| SOA | 1 | ns1.netnames.net hostmaster.cscdns.net |
Analysis
IP Addresses
cloud-process.com resolves to the IP addresses 165.160.13.20 and 165.160.15.20
Two other host names, along with chipotle20.com, valvoline.co.uk and curiobiosciences.org, also share IP numbers with cloud-process.com.
Name Servers
The NS records for cloud-process.com point to four name servers: ns1.netnames.net, ns2.netnames.net, ns5.netnames.net and ns6.netnames.net.
cloud-process.com partially shares its NS delegation with several other domains, including lambi.ru, wtmlatinamerica.com, condair.org and two others.
These name servers are regularly seen alongside ns7.netnames.net and ns8.netnames.net as name servers.
Each of ns1.netnames.net, ns2.netnames.net, ns5.netnames.net and ns6.netnames.net resolves to two IP numbers, falling into two groups: ns1.netnames.net and ns5.netnames.net share 156.154.130.100 and 2610:a1:1022::100, while ns2.netnames.net and ns6.netnames.net share 156.154.131.100 and 2610:a1:1023::100.
Both ns1.netnames.net and ns5.netnames.net resolve to 2610:a1:1022::100 IP addresses each.
Both ns1.netnames.net and ns5.netnames.net resolve to 156.154.130.100 IP addresses each.
Both ns2.netnames.net and ns6.netnames.net resolve to 2610:a1:1023::100 IP addresses each.
Both ns2.netnames.net and ns6.netnames.net resolve to 156.154.131.100 IP addresses each.
Mail Servers
cloud-process.com is served by two mail servers, relay1.netnames.net and relay2.netnames.net.
Among the domains sharing a mail server setup with cloud-process.com are eastangliafivewindfarm.com, in-nam20.com, vpriv.com and two others.
At least a portion of cloud-process.com's mail servers are also used by other domains, for example vanstatuscheck.co.uk.
relay1.netnames.net resolves to 185.26.230.83. relay2.netnames.net resolves to 185.26.230.89. Both host names point to a single IP number.