`bellclearing.com`

DNSSEC	⚠️ Not signed
NS	`ns1.p17.dynect.net` ⚠️ Not in zone NS records
		A	2600:2000:2100::ca^{🇺🇸 ORACLE-OCI-318982600:2000:2100::/44 Dynamic Network Services, Inc.}
			PTR	`ns1.p202.dns.oraclecloud.net`
		A	108.59.166.202^{🇺🇸 ORACLE-OCI-31898108.59.166.0/23 Dynamic Network Services, Inc.}
			PTR	`ns1.p202.dns.oraclecloud.net`
NS	`ns2.p17.dynect.net` ⚠️ Not in zone NS records
		A	2600:2000:2110::ca^{🇺🇸 ORACLE-OCI-318982600:2000:2110::/44 Dynamic Network Services, Inc.}
			PTR	`ns2.p202.dns.oraclecloud.net`
		A	108.59.168.202^{🇺🇸 ORACLE-OCI-31898108.59.168.0/23 Dynamic Network Services, Inc.}
			PTR	`ns2.p202.dns.oraclecloud.net`
NS	`ns3.p17.dynect.net` ⚠️ Not in zone NS records
		A	2600:2000:2120::ca^{🇺🇸 ORACLE-OCI-318982600:2000:2120::/44 Dynamic Network Services, Inc.}
			PTR	`ns3.p202.dns.oraclecloud.net`
		A	108.59.170.202^{🇺🇸 ORACLE-OCI-31898108.59.170.0/23 Dynamic Network Services, Inc.}
			PTR	`ns3.p202.dns.oraclecloud.net`
NS	`ns4.p17.dynect.net` ⚠️ Not in zone NS records
		A	2600:2000:2130::ca^{🇺🇸 ORACLE-OCI-318982600:2000:2130::/44 Dynamic Network Services, Inc.}
			PTR	`ns4.p202.dns.oraclecloud.net`
		A	108.59.172.202^{🇺🇸 ORACLE-OCI-31898108.59.172.0/23 Dynamic Network Services, Inc.}
			PTR	`ns4.p202.dns.oraclecloud.net`

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

Same first word

bellclearing.com

Similar names

rebelcalling.io

rebelcalling.org

rebelcalling.net

rebelcalling.com

DNS History

4 records (4 active, 0 former)

●NSns1.p17.dynect.net2026-03-07 → 2026-05-10 · 2 obs

● 2026-03-07 16:38:06
● 2026-05-10 18:23:28

●NSns2.p17.dynect.net2026-03-07 → 2026-05-10 · 2 obs

● 2026-03-07 16:38:06
● 2026-05-10 18:23:28

●NSns3.p17.dynect.net2026-03-07 → 2026-05-10 · 2 obs

● 2026-03-07 16:38:06
● 2026-05-10 18:23:28

●NSns4.p17.dynect.net2026-03-07 → 2026-05-10 · 2 obs

● 2026-03-07 16:38:06
● 2026-05-10 18:23:28

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, k.gtld-servers.net...	-
bellclearing.com	ns1.p17.dynect.net, ns3.p17.dynect.net, ns2.p17.dynect.net, ns4.p17.dynect.net	-

✅ Authoritative Response

Server:108.59.166.202

NS records: ns1.p17.dynect.net, ns3.p17.dynect.net, ns2.p17.dynect.net, ns4.p17.dynect.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for bellclearing.com (unsigned zone)

⏱️ Timing

Total: 915ms | Queries: -

📄 Records

Type	Count	Sample Data

Analysis

Name Servers

bellclearing.com is delegated to four name servers: ns1.p17.dynect.net, ns2.p17.dynect.net, ns3.p17.dynect.net and ns4.p17.dynect.net.

bellclearing.com shares name servers with other domains at least partially, for example mtsmondo.com, coloradocustomcoating.com, mandarinorientalbrazil.com, marketvision.net and pti-ns-triprequest.com.

these name servers are commonly used together with the name servers ednsmw01.rightnowtech.com, ednsmw02.rightnowtech.com, ednsvipch01.rightnowtech.com, ns1.p68.dns.oraclecloud.net, ns2.p68.dns.oraclecloud.net, ns3.p68.dns.oraclecloud.net, ns4.p68.dns.oraclecloud.net and dns1.western.edu.

Host names with two IP numbers:

ns1.p17.dynect.net points to: 2600:2000:2100::ca and 108.59.166.202

ns2.p17.dynect.net points to: 2600:2000:2110::ca and 108.59.168.202

ns3.p17.dynect.net points to: 2600:2000:2120::ca and 108.59.170.202

ns4.p17.dynect.net points to: 2600:2000:2130::ca and 108.59.172.202

bellclearing.com - robtex.com