`chiefoperator.com`

DNSSEC	⚠️ Not signed
A	13.248.169.48^{🇺🇸 Amazon13.248.160.0/20}
		PTR	`a904c694c05102f30.awsglobalaccelerator.com`
A	76.223.54.146^{🇺🇸 Amazon76.223.48.0/20}
NS	`ns2.afternic.com` ⭐
		A	2603:5:2226::45^{🇺🇸 GODADDY-DNS2603:5:2220::/44}
			PTR	`ns2.afternic.com`
		A	173.201.66.69^{🇺🇸 GODADDY-DNS173.201.66.0/23}
			PTR	`ns2.afternic.com`
NS	`ns1.afternic.com`
		A	2603:5:2126::45^{🇺🇸 GODADDY-DNS2603:5:2120::/44}
			PTR	`ns1.afternic.com`
		A	97.74.98.69^{🇺🇸 GODADDY-DNS97.74.98.0/23}
			PTR	`ns1.afternic.com`
TXT	`v=spf1 -all`
SOA	`ns2.afternic.com`dns@jomax.net serial=1

`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=1774378472

Subdomains

linknet.chiefoperator.com

best.chiefoperator.com

channel.chiefoperator.com

DNS History

20 records (4 active, 16 former)

●NSns1.afternic.com2026-03-24 → 2026-03-24 · 3 obs

○ 2018-09-08 15:54:38
● 2026-03-24 19:11:22
● 2026-03-24 19:11:24

○NSns1.whois.com2018-09-08 → 2018-09-08 · 4 obs

○ 2017-01-13 03:25:00
● 2018-09-08 15:54:38
○ 2026-03-24 19:11:22
○ 2026-03-24 19:11:24

●NSns2.afternic.com2026-03-24 → 2026-03-24 · 3 obs

○ 2018-09-08 15:54:38
● 2026-03-24 19:11:22
● 2026-03-24 19:11:24

○NSns2.whois.com2018-09-08 → 2018-09-08 · 4 obs

○ 2017-01-13 03:25:00
● 2018-09-08 15:54:38
○ 2026-03-24 19:11:22
○ 2026-03-24 19:11:24

○NSns3.whois.com2018-09-08 → 2018-09-08 · 4 obs

○ 2017-01-13 03:25:00
● 2018-09-08 15:54:38
○ 2026-03-24 19:11:22
○ 2026-03-24 19:11:24

○NSns4.whois.com2018-09-08 → 2018-09-08 · 4 obs

○ 2017-01-13 03:25:00
● 2018-09-08 15:54:38
○ 2026-03-24 19:11:22
○ 2026-03-24 19:11:24

○NSns51.1and1.com2015-07-22 → 2017-01-13 · 4 obs

● 2015-07-22 00:16:12
● 2017-01-13 03:25:00
○ 2018-09-08 15:54:38
○ 2026-03-24 19:11:24

○NSns52.1and1.com2015-07-22 → 2017-01-13 · 4 obs

● 2015-07-22 00:16:12
● 2017-01-13 03:25:00
○ 2018-09-08 15:54:38
○ 2026-03-24 19:11:24

○MXmx00.1and1.com2015-07-22 → 2017-01-13 · 4 obs

● 2015-07-22 00:16:12
● 2017-01-13 03:25:00
○ 2018-09-08 15:54:38
○ 2026-03-24 19:11:24

○MXmx01.1and1.com2015-07-22 → 2017-01-13 · 4 obs

● 2015-07-22 00:16:12
● 2017-01-13 03:25:00
○ 2018-09-08 15:54:38
○ 2026-03-24 19:11:24

○MXus2.mx1.mailhostbox.com2018-09-08 → 2018-09-08 · 4 obs

○ 2017-01-13 03:25:00
● 2018-09-08 15:54:38
○ 2026-03-24 19:11:22
○ 2026-03-24 19:11:24

○MXus2.mx2.mailhostbox.com2018-09-08 → 2018-09-08 · 4 obs

○ 2017-01-13 03:25:00
● 2018-09-08 15:54:38
○ 2026-03-24 19:11:22
○ 2026-03-24 19:11:24

○MXus2.mx3.mailhostbox.com2018-09-08 → 2018-09-08 · 4 obs

○ 2017-01-13 03:25:00
● 2018-09-08 15:54:38
○ 2026-03-24 19:11:22
○ 2026-03-24 19:11:24

●A13.248.169.482026-03-24 → 2026-03-24 · 3 obs

○ 2018-09-08 15:54:38
● 2026-03-24 19:11:22
● 2026-03-24 19:11:24

○A192.195.77.1712016-05-03 → 2017-01-13 · 5 obs

○ 2015-12-02 00:40:12
● 2016-05-03 05:10:26
● 2017-01-13 03:25:00
○ 2018-09-08 15:54:38
○ 2026-03-24 19:11:24

○A198.71.55.202015-07-22 → 2015-12-02 · 4 obs

● 2015-07-22 00:16:12
● 2015-12-02 00:40:12
○ 2016-05-03 05:10:26
○ 2026-03-24 19:11:24

○A207.174.213.342018-09-08 → 2018-09-08 · 4 obs

○ 2017-01-13 03:25:00
● 2018-09-08 15:54:38
○ 2026-03-24 19:11:22
○ 2026-03-24 19:11:24

○A2607:f1c0:1000:40de:535a:3af:9fae:e8092015-07-22 → 2015-12-02 · 4 obs

● 2015-07-22 00:16:12
● 2015-12-02 00:40:12
○ 2016-05-03 05:10:26
○ 2026-03-24 19:11:24

○A2607:f1c0:1000:40de:c061:f370:7fcb:482c2016-05-03 → 2017-01-13 · 5 obs

○ 2015-12-02 00:40:12
● 2016-05-03 05:10:26
● 2017-01-13 03:25:00
○ 2018-09-08 15:54:38
○ 2026-03-24 19:11:24

●A76.223.54.1462026-03-24 → 2026-03-24 · 3 obs

○ 2018-09-08 15:54:38
● 2026-03-24 19:11:22
● 2026-03-24 19:11:24

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	f.gtld-servers.net, c.gtld-servers.net, j.gtld-servers.net, b.gtld-servers.net...	-
chiefoperator.com	ns1.afternic.com, ns2.afternic.com	4 records

✅ Authoritative Response

Server:173.201.66.69

NS records: ns1.afternic.com, ns2.afternic.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for chiefoperator.com (unsigned zone)

⏱️ Timing

Total: 253ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`76.223.54.146, 13.248.169.48`
NS	2	`ns1.afternic.com, ns2.afternic.com`
MX	1	`. (pri: 0)`
TXT	1	`v=spf1 -all`
SOA	1	`ns2.afternic.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns1.afternic.com, ns1.afternic.com, ns2.afternic.com...)

Analysis

Hierarchy

chiefoperator.com is the parent of linknet.chiefoperator.com, best.chiefoperator.com and channel.chiefoperator.com.

IP Addresses

chiefoperator.com resolves to two IP numbers: 13.248.169.48 and 76.223.54.146.

other host names including tastybites.net, mutfagi.com, ttap.org, dubshopinc.com and cropress.com share IP numbers with chiefoperator.com.

Name Servers

chiefoperator.com is delegated to two name servers ns1.afternic.com and ns2.afternic.com.

chiefoperator.com shares the same name server setup as other domains, for instance auve.net, docdon.com, savemee.in, vetty.org and jafc.net.

chiefoperator.com at least partially shares name servers with other domains, for instance ivc.info, voon.net, leopard-lodge.com, retention.info and rno.info.

These name servers are commonly used with verification-q2yfbmuxrvnsdnaogqtqft.ns101.verify.hn, verification-w2xf9gdmxas2ndpt8ztrdm.ns101.verify.hn and verification-m82hxdvunam48exysiuc59.ns101.verify.hn.

Host names with two IP numbers:

The host name ns1.afternic.com points to 2603:5:2126::45 and 97.74.98.69; the host name ns2.afternic.com points to 2603:5:2226::45 and 173.201.66.69.

chiefoperator.com - robtex.com