consequence-project.com - dns.ninja
consequence-project.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=1786081829 | ||||||
Same first word
consequence-project.com |
consequence-project.net |
consequence-project.org |
DNS History
17 records (9 active, 8 former)
βNSns1-06.azure-dns.com2026-02-28 β 2026-08-07 Β· 3 obs
β 2026-02-28 15:03:28
β 2026-08-07 05:59:38
βNSns1.msft.net2015-05-27 β 2017-05-19 Β· 4 obs
β 2017-05-19 17:25:32
β 2026-02-28 15:03:28
β 2026-08-07 05:59:38
βNSns2-06.azure-dns.net2026-02-28 β 2026-08-07 Β· 3 obs
β 2026-02-28 15:03:28
β 2026-08-07 05:59:38
βNSns2.msft.net2015-05-27 β 2017-05-19 Β· 4 obs
β 2017-05-19 17:25:32
β 2026-02-28 15:03:28
β 2026-08-07 05:59:38
βNSns3-06.azure-dns.org2026-02-28 β 2026-08-07 Β· 3 obs
β 2026-02-28 15:03:28
β 2026-08-07 05:59:38
βNSns3.msft.net2015-05-27 β 2017-05-19 Β· 4 obs
β 2017-05-19 17:25:32
β 2026-02-28 15:03:28
β 2026-08-07 05:59:38
βNSns4-06.azure-dns.info2026-02-28 β 2026-08-07 Β· 3 obs
β 2026-02-28 15:03:28
β 2026-08-07 05:59:38
βNSns4.msft.net2015-05-27 β 2017-05-19 Β· 4 obs
β 2017-05-19 17:25:32
β 2026-02-28 15:03:28
β 2026-08-07 05:59:38
βA20.112.250.1332026-02-28 β 2026-08-07 Β· 3 obs
β 2026-02-28 15:03:28
β 2026-08-07 05:59:38
βA20.231.239.2462026-02-28 β 2026-08-07 Β· 3 obs
β 2026-02-28 15:03:28
β 2026-08-07 05:59:38
βA20.236.44.1622026-02-28 β 2026-08-07 Β· 3 obs
β 2026-02-28 15:03:28
β 2026-08-07 05:59:38
βA20.70.246.202026-02-28 β 2026-08-07 Β· 3 obs
β 2026-02-28 15:03:28
β 2026-08-07 05:59:38
βA20.76.201.1712026-02-28 β 2026-08-07 Β· 3 obs
β 2026-02-28 15:03:28
β 2026-08-07 05:59:38
βA40.84.199.2332017-05-19 β 2017-05-19 Β· 4 obs
β 2017-05-19 17:25:32
β 2026-02-28 15:03:28
β 2026-08-07 05:59:38
βA52.178.167.1092017-05-19 β 2017-05-19 Β· 4 obs
β 2017-05-19 17:25:32
β 2026-02-28 15:03:28
β 2026-08-07 05:59:38
βA64.4.6.1002015-05-27 β 2016-09-24 Β· 4 obs
β 2016-09-24 13:42:32
β 2017-05-19 17:25:32
β 2026-08-07 05:59:38
βA65.55.39.102015-05-27 β 2016-09-24 Β· 4 obs
β 2016-09-24 13:42:32
β 2017-05-19 17:25:32
β 2026-08-07 05:59:38
π DNS Trace
Analysis
IP Addresses
consequence-project.com directs to five IP numbers, including 20.70.246.20, 20.76.201.171, 20.112.250.133 and two others
bingyahoonetwork.co.ve, microsofthealth.fr, msngamecenter.com.mx plus two other host names have IP numbers in common with consequence-project.com.
Name Servers
Four name servers handle the delegation for consequence-project.com: ns1-06.azure-dns.com, ns4-06.azure-dns.info, ns2-06.azure-dns.net and ns3-06.azure-dns.org.
At least some of consequence-project.com's name servers are shared with other domains, for example hyderus.com, dwpautomation.com, 65.29.20.in-addr.arpa and two more.
Four hostnames, each resolving to a pair of IP addresses: ns1-06.azure-dns.com directs to 13.107.236.6 and 2603:1061:0:700::6; ns4-06.azure-dns.info directs to 208.84.5.6 and 2620:1ec:bda:700::6; ns2-06.azure-dns.net directs to 150.171.21.6 and 2620:1ec:8ec:700::6; ns3-06.azure-dns.org directs to 204.14.183.6 and 2a01:111:4000:700::6.