progress-linux.net - dns.ninja

`progress-linux.net`

DNSSEC	⚠️ Not signed
A	2a13:181::105^{🇨🇭 bfh2a13:181::/32}
		PTR	`web-redirect.as216318.net`
A	138.124.176.105^{🇨🇭 bfh138.124.176.0/24}
NS	`ns1.as216318.net` ⭐
		A	2a13:181::101^{🇨🇭 bfh2a13:181::/32}
			PTR	`ns1.as216318.net`
		A	138.124.176.101^{🇨🇭 bfh138.124.176.0/24}
			PTR	`ns1.as216318.net`
NS	`ns.as216318.net`
		A	2a13:181::101^{🇨🇭 bfh2a13:181::/32}
			PTR	`ns1.as216318.net`
		A	2a13:181::102^{🇨🇭 bfh2a13:181::/32}
			PTR	`ns2.as216318.net`
		A	2a13:181::103^{🇨🇭 bfh2a13:181::/32}
			PTR	`ns3.as216318.net`
		A	2a13:181::104^{🇨🇭 bfh2a13:181::/32}
			PTR	`ns4.as216318.net`
		A	138.124.176.101^{🇨🇭 bfh138.124.176.0/24}
			PTR	`ns1.as216318.net`
		A	138.124.176.102^{🇨🇭 bfh138.124.176.0/24}
			PTR	`ns2.as216318.net`
		A	138.124.176.103^{🇨🇭 bfh138.124.176.0/24}
			PTR	`ns3.as216318.net`
		A	138.124.176.104^{🇨🇭 bfh138.124.176.0/24}
			PTR	`ns4.as216318.net`
NS	`ns2.as216318.net`
		A	2a13:181::102^{🇨🇭 bfh2a13:181::/32}
			PTR	`ns2.as216318.net`
		A	138.124.176.102^{🇨🇭 bfh138.124.176.0/24}
			PTR	`ns2.as216318.net`
NS	`ns3.as216318.net`
		A	2a13:181::103^{🇨🇭 bfh2a13:181::/32}
			PTR	`ns3.as216318.net`
		A	138.124.176.103^{🇨🇭 bfh138.124.176.0/24}
			PTR	`ns3.as216318.net`
NS	`ns4.as216318.net`
		A	2a13:181::104^{🇨🇭 bfh2a13:181::/32}
			PTR	`ns4.as216318.net`
		A	138.124.176.104^{🇨🇭 bfh138.124.176.0/24}
			PTR	`ns4.as216318.net`
SOA	`ns.as216318.net`sysadmin@as216318.net serial=0

`net`

	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.net`nstld@verisign-grs.com serial=1781032883

Same first word

progress-linux.net

progress-linux.org

progress-linux.ch

progress-linux.info

DNS History

21 records (7 active, 14 former)

○NSdns-master.open-infrastructure.net2016-02-01 → 2017-01-31 · 5 obs

○ 2015-11-05 01:26:14
● 2016-02-01 10:22:18
● 2017-01-31 09:41:32
○ 2026-03-22 18:00:48
○ 2026-06-09 19:44:16

○NSdns1.open-infrastructure.net2016-02-01 → 2017-01-31 · 5 obs

○ 2015-11-05 01:26:14
● 2016-02-01 10:22:18
● 2017-01-31 09:41:32
○ 2026-03-22 18:00:48
○ 2026-06-09 19:44:16

○NSdns2.open-infrastructure.net2016-02-01 → 2017-01-31 · 5 obs

○ 2015-11-05 01:26:14
● 2016-02-01 10:22:18
● 2017-01-31 09:41:32
○ 2026-03-22 18:00:48
○ 2026-06-09 19:44:16

○NSdns3.open-infrastructure.net2016-02-01 → 2017-01-31 · 5 obs

○ 2015-11-05 01:26:14
● 2016-02-01 10:22:18
● 2017-01-31 09:41:32
○ 2026-03-22 18:00:48
○ 2026-06-09 19:44:16

○NSname-master.open-infrastructure.net2015-06-29 → 2015-11-05 · 4 obs

● 2015-06-29 00:51:14
● 2015-11-05 01:26:14
○ 2016-02-01 10:22:18
○ 2026-06-09 19:44:16

○NSname1.open-infrastructure.net2015-06-29 → 2015-11-05 · 4 obs

● 2015-06-29 00:51:14
● 2015-11-05 01:26:14
○ 2016-02-01 10:22:18
○ 2026-06-09 19:44:16

○NSname2.open-infrastructure.net2015-06-29 → 2015-11-05 · 4 obs

● 2015-06-29 00:51:14
● 2015-11-05 01:26:14
○ 2016-02-01 10:22:18
○ 2026-06-09 19:44:16

○NSname3.open-infrastructure.net2015-06-29 → 2015-11-05 · 4 obs

● 2015-06-29 00:51:14
● 2015-11-05 01:26:14
○ 2016-02-01 10:22:18
○ 2026-06-09 19:44:16

●NSns.as216318.net2026-03-22 → 2026-06-09 · 3 obs

○ 2017-01-31 09:41:32
● 2026-03-22 18:00:48
● 2026-06-09 19:44:16

●NSns1.as216318.net2026-03-22 → 2026-06-09 · 3 obs

○ 2017-01-31 09:41:32
● 2026-03-22 18:00:48
● 2026-06-09 19:44:16

●NSns2.as216318.net2026-03-22 → 2026-06-09 · 3 obs

○ 2017-01-31 09:41:32
● 2026-03-22 18:00:48
● 2026-06-09 19:44:16

●NSns3.as216318.net2026-03-22 → 2026-06-09 · 3 obs

○ 2017-01-31 09:41:32
● 2026-03-22 18:00:48
● 2026-06-09 19:44:16

●NSns4.as216318.net2026-03-22 → 2026-06-09 · 3 obs

○ 2017-01-31 09:41:32
● 2026-03-22 18:00:48
● 2026-06-09 19:44:16

○MXmail-redirect.open-infrastructure.net2015-11-05 → 2017-01-31 · 4 obs

● 2015-11-05 01:26:14
● 2017-01-31 09:41:32
○ 2026-03-22 18:00:48
○ 2026-06-09 19:44:16

●A138.124.176.1052026-04-26 → 2026-06-09 · 3 obs

○ 2026-04-11 17:22:28
● 2026-04-26 21:14:02
● 2026-06-09 19:44:16

○A138.124.176.2182026-03-22 → 2026-04-11 · 5 obs

○ 2017-01-31 09:41:32
● 2026-03-22 18:00:48
● 2026-04-11 17:22:28
○ 2026-04-26 21:14:02
○ 2026-06-09 19:44:16

○A212.83.45.102015-06-29 → 2015-11-05 · 4 obs

● 2015-06-29 00:51:14
● 2015-11-05 01:26:14
○ 2016-02-01 10:22:18
○ 2026-06-09 19:44:16

○A212.83.45.162016-02-01 → 2016-02-01 · 4 obs

○ 2015-11-05 01:26:14
● 2016-02-01 10:22:18
○ 2016-06-20 10:57:16
○ 2026-06-09 19:44:16

●A2a13:181::1052026-04-26 → 2026-06-09 · 3 obs

○ 2026-04-11 17:22:28
● 2026-04-26 21:14:02
● 2026-06-09 19:44:16

○A2a13:181::2182026-03-22 → 2026-04-11 · 5 obs

○ 2017-01-31 09:41:32
● 2026-03-22 18:00:48
● 2026-04-11 17:22:28
○ 2026-04-26 21:14:02
○ 2026-06-09 19:44:16

○A62.113.201.112016-06-20 → 2017-01-31 · 5 obs

○ 2016-02-01 10:22:18
● 2016-06-20 10:57:16
● 2017-01-31 09:41:32
○ 2026-03-22 18:00:48
○ 2026-06-09 19:44:16

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
net	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
progress-linux.net	ns1.as216318.net, ns2.as216318.net, ns3.as216318.net, ns4.as216318.net	8 records

✅ Authoritative Response

Server:138.124.176.104

NS records: ns1.as216318.net, ns2.as216318.net, ns3.as216318.net, ns4.as216318.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for progress-linux.net (unsigned zone)

⏱️ Timing

Total: 334ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`138.124.176.105`
AAAA	1	`2a13:181::105`
NS	4	`ns1.as216318.net, ns2.as216318.net...`
SOA	1	`ns.as216318.net sysadmin.as216318.net`

📌 Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (ns1.as216318.net, ns1.as216318.net, ns2.as216318.net...)

Analysis

IP Addresses

progress-linux.net points to two IP numbers: 138.124.176.105 and 2a13:181::105.

Two other host names, along with open-infrastructure.org, open-infrastructure.ch and web-redirect.as216318.net, also share IP numbers with progress-linux.net.

Name Servers

Authority for progress-linux.net is spread across 5 name servers; listed: ns1.as216318.net, ns2.as216318.net, ns3.as216318.net and two others.

There is at least partial name server overlap between progress-linux.net and other domains — 127011.org, 0.0.0.0.1.8.1.0.3.1.a.2.ip6.arpa, open-infrastructure.org and two more among them.

These name servers frequently co-occur with the name servers ns4.as216318.net and ns.as216318.net.

DNS names with 8 IP addresses:

ns.as216318.net maps to 138.124.176.101, 138.124.176.102, 138.124.176.103 and five more IP addresses.

Host names that have two IP addresses:

ns1.as216318.net directs traffic to 138.124.176.101 and 2a13:181::101.

ns2.as216318.net directs traffic to 138.124.176.102 and 2a13:181::102.

ns3.as216318.net directs traffic to 138.124.176.103 and 2a13:181::103.

ns4.as216318.net directs traffic to 138.124.176.104 and 2a13:181::104.

Both ns.as216318.net and ns1.as216318.net resolve to 2a13:181::101 IP addresses each.

Both ns.as216318.net and ns2.as216318.net resolve to 2a13:181::102 IP addresses each.

Both ns.as216318.net and ns3.as216318.net resolve to 2a13:181::103 IP addresses each.

Both ns.as216318.net and ns4.as216318.net resolve to 2a13:181::104 IP addresses each.

Both ns.as216318.net and ns1.as216318.net resolve to 138.124.176.101 IP addresses each.

Both ns.as216318.net and ns2.as216318.net resolve to 138.124.176.102 IP addresses each.

Both ns.as216318.net and ns3.as216318.net resolve to 138.124.176.103 IP addresses each.

Both ns.as216318.net and ns4.as216318.net resolve to 138.124.176.104 IP addresses each.