`bashetsconnection.com`

DNSSEC	⚠️ Not signed
NS	`ns1.amgen.com` ⚠️ Not in zone NS records
		A	138.133.52.91^{🇺🇸 AS14762138.133.52.0/24 Switch Communications Customer Route}
			PTR	`ns1.amgen.com`
NS	`ns2.amgen.com` ⚠️ Not in zone NS records
		A	138.133.61.100^{🇺🇸 AS14762138.133.61.0/24}
			PTR	`ns2.amgen.com`
NS	`ns3.amgen.com` ⚠️ Not in zone NS records
		A	138.133.194.6^{🇺🇸 AS14762138.133.194.0/24 PNAP-AMS004 Amgen Route}
			PTR	`ns3.amgen.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.net`nstld@verisign-grs.com serial=1780663074

Same first word

bashetsconnection.com

DNS History

8 records (3 active, 5 former)

○NSdns1.cscdns.net2018-12-16 → 2018-12-16 · 3 obs

● 2018-12-16 00:27:08
○ 2026-05-29 18:19:38
○ 2026-06-05 12:45:44

○NSdns2.cscdns.net2018-12-16 → 2018-12-16 · 3 obs

● 2018-12-16 00:27:08
○ 2026-05-29 18:19:38
○ 2026-06-05 12:45:44

●NSns1.amgen.com2026-05-29 → 2026-06-05 · 3 obs

○ 2018-12-16 00:27:08
● 2026-05-29 18:19:38
● 2026-06-05 12:45:44

●NSns2.amgen.com2026-05-29 → 2026-06-05 · 3 obs

○ 2018-12-16 00:27:08
● 2026-05-29 18:19:38
● 2026-06-05 12:45:44

●NSns3.amgen.com2026-05-29 → 2026-06-05 · 3 obs

○ 2018-12-16 00:27:08
● 2026-05-29 18:19:38
● 2026-06-05 12:45:44

○MXcustmx.cscdns.net2018-12-16 → 2018-12-16 · 3 obs

● 2018-12-16 00:27:08
○ 2026-05-29 18:19:38
○ 2026-06-05 12:45:44

○A165.160.13.202018-12-16 → 2018-12-16 · 3 obs

● 2018-12-16 00:27:08
○ 2026-05-29 18:19:38
○ 2026-06-05 12:45:44

○A165.160.15.202018-12-16 → 2018-12-16 · 3 obs

● 2018-12-16 00:27:08
○ 2026-05-29 18:19:38
○ 2026-06-05 12:45:44

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
bashetsconnection.com	ns1.amgen.com, ns2.amgen.com, ns3.amgen.com	3 records

✅ Authoritative Response

Server:138.133.194.6

NS records: ns1.amgen.com, ns2.amgen.com, ns3.amgen.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for bashetsconnection.com (unsigned zone)

⏱️ Timing

Total: 3472ms | Queries: -

📄 Records

Type	Count	Sample Data

📌 Glue Records Collected

Total: 3

Out-of-bailiwick: 3 (ns1.amgen.com, ns2.amgen.com, ns3.amgen.com)

Analysis

Name Servers

bashetsconnection.com is delegated to three name servers: ns1.amgen.com, ns2.amgen.com and ns3.amgen.com.

At least some of bashetsconnection.com's name servers are shared with other domains, for example amgenitregistry.com, management-anemie.com.fr, lumakras.com.cn and two more.

These name servers tend to be used in conjunction with the name servers ns0-can.amgen.com.

ns1.amgen.com, ns2.amgen.com and ns3.amgen.com each resolve to a single IP address: ns1.amgen.com resolves to 138.133.52.91, ns2.amgen.com resolves to 138.133.61.100 and ns3.amgen.com resolves to 138.133.194.6.

bashetsconnection.com - robtex.com