`silverbells.com`

DNSSEC	⚠️ Not signed
A	2606:4700:3031::ac43:c49e^{🇺🇸 Cloudflare2606:4700:3031::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3032::6815:3c7e^{🇺🇸 Cloudflare2606:4700:3032::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.60.126^{Cloudflare104.21.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.196.158^{🇺🇸 Cloudflare172.67.192.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`gwen.ns.cloudflare.com` ⭐
		A	2606:4700:50::adf5:3aa0^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`gwen.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c0a0^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`gwen.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:20a0^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`gwen.ns.cloudflare.com`
		A	108.162.192.160^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`gwen.ns.cloudflare.com`
		A	172.64.32.160^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`gwen.ns.cloudflare.com`
		A	173.245.58.160^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`gwen.ns.cloudflare.com`
NS	`ivan.ns.cloudflare.com`
		A	2606:4700:58::adf5:3b78^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ivan.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c178^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`ivan.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2178^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`ivan.ns.cloudflare.com`
		A	108.162.193.120^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ivan.ns.cloudflare.com`
		A	172.64.33.120^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ivan.ns.cloudflare.com`
		A	173.245.59.120^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ivan.ns.cloudflare.com`
MX	`silverbells-com.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c91d::a^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-co1pr21cu00202.inbound.protection.outlook.com`
		A	2a01:111:f403:c936::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-cy1pr05cu00400.inbound.protection.outlook.com`
		A	2a01:111:f403:c946::7^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-ch5pr02cu00307.inbound.protection.outlook.com`
		A	2a01:111:f403:f912::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-cy5pr03cu00200.inbound.protection.outlook.com`
		A	52.101.9.0^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bl2pr02cu00100.inbound.protection.outlook.com`
		A	52.101.9.14^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bl0pr03cu00206.inbound.protection.outlook.com`
		A	52.101.10.6^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bn1pr21cu00106.inbound.protection.outlook.com`
		A	52.101.11.13^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sn1pr0501cu00205.inbound.protection.outlook.com`
TXT	`MS=ms57520339`
TXT	`google-site-verification=ez9UxcCYDB-V-8z9djAhU5tOmhPgF04bSMz7EVjLwOk`
TXT	`v=spf1 include:spf.protection.outlook.com -all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4	104.21.60.126, 172.67.196.158
		IPv6	2606:4700:3031::ac43:c49e, 2606:4700:3032::6815:3c7e
SOA	`gwen.ns.cloudflare.com`dns@cloudflare.com serial=2398499262

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

Previously MX for

silverbells.com

Same first word

silverbells.com

silverbells.com.my

DNS History

34 records (7 active, 27 former)

○NSdns1.name-services.com2016-02-27 → 2016-02-27 · 4 obs

○ 2015-11-19 09:27:32
● 2016-02-27 10:57:44
○ 2016-06-26 15:01:48
○ 2026-03-24 22:09:22

○NSdns2.name-services.com2016-02-27 → 2016-02-27 · 4 obs

○ 2015-11-19 09:27:32
● 2016-02-27 10:57:44
○ 2016-06-26 15:01:48
○ 2026-03-24 22:09:22

○NSdns3.name-services.com2016-02-27 → 2016-02-27 · 4 obs

○ 2015-11-19 09:27:32
● 2016-02-27 10:57:44
○ 2016-06-26 15:01:48
○ 2026-03-24 22:09:22

○NSdns4.name-services.com2016-02-27 → 2016-02-27 · 4 obs

○ 2015-11-19 09:27:32
● 2016-02-27 10:57:44
○ 2016-06-26 15:01:48
○ 2026-03-24 22:09:22

○NSdns5.name-services.com2016-02-27 → 2016-02-27 · 4 obs

○ 2015-11-19 09:27:32
● 2016-02-27 10:57:44
○ 2016-06-26 15:01:48
○ 2026-03-24 22:09:22

●NSgwen.ns.cloudflare.com2026-02-19 → 2026-03-24 · 3 obs

○ 2019-03-28 22:51:36
● 2026-02-19 18:20:34
● 2026-03-24 22:09:22

●NSivan.ns.cloudflare.com2026-02-19 → 2026-03-24 · 3 obs

○ 2019-03-28 22:51:36
● 2026-02-19 18:20:34
● 2026-03-24 22:09:22

○NSns.silverbells.com2016-06-26 → 2016-06-26 · 4 obs

○ 2016-02-27 10:57:44
● 2016-06-26 15:01:48
○ 2017-02-12 23:31:54
○ 2026-03-24 22:09:22

○NSns1.brmcnetworks.com2019-03-28 → 2019-03-28 · 4 obs

○ 2017-02-12 23:31:54
● 2019-03-28 22:51:36
○ 2026-02-19 18:20:34
○ 2026-03-24 22:09:22

○NSns1.trafficz.com2007-11-01 → 2015-11-19 · 4 obs

● 2007-11-01 00:08:26
● 2015-11-19 09:27:32
○ 2016-02-27 10:57:44
○ 2026-03-24 22:09:22

○NSns2.brmcnetworks.com2019-03-28 → 2019-03-28 · 4 obs

○ 2017-02-12 23:31:54
● 2019-03-28 22:51:36
○ 2026-02-19 18:20:34
○ 2026-03-24 22:09:22

○NSns2.trafficz.com2007-11-01 → 2015-11-19 · 4 obs

● 2007-11-01 00:08:26
● 2015-11-19 09:27:32
○ 2016-02-27 10:57:44
○ 2026-03-24 22:09:22

○NSns3.brmcnetworks.com2019-03-28 → 2019-03-28 · 4 obs

○ 2017-02-12 23:31:54
● 2019-03-28 22:51:36
○ 2026-02-19 18:20:34
○ 2026-03-24 22:09:22

○NSns3.epik.com2016-06-26 → 2017-02-12 · 5 obs

○ 2016-02-27 10:57:44
● 2016-06-26 15:01:48
● 2017-02-12 23:31:54
○ 2019-03-28 22:51:36
○ 2026-03-24 22:09:22

○NSns4.epik.com2016-06-26 → 2017-02-12 · 5 obs

○ 2016-02-27 10:57:44
● 2016-06-26 15:01:48
● 2017-02-12 23:31:54
○ 2019-03-28 22:51:36
○ 2026-03-24 22:09:22

○MXalt1.aspmx.l.google.com2019-03-28 → 2019-03-28 · 4 obs

○ 2017-02-12 23:31:54
● 2019-03-28 22:51:36
○ 2026-02-19 18:20:34
○ 2026-03-24 22:09:22

○MXalt2.aspmx.l.google.com2019-03-28 → 2019-03-28 · 4 obs

○ 2017-02-12 23:31:54
● 2019-03-28 22:51:36
○ 2026-02-19 18:20:34
○ 2026-03-24 22:09:22

○MXaspmx.l.google.com2019-03-28 → 2019-03-28 · 4 obs

○ 2017-02-12 23:31:54
● 2019-03-28 22:51:36
○ 2026-02-19 18:20:34
○ 2026-03-24 22:09:22

○MXaspmx2.googlemail.com2019-03-28 → 2019-03-28 · 4 obs

○ 2017-02-12 23:31:54
● 2019-03-28 22:51:36
○ 2026-02-19 18:20:34
○ 2026-03-24 22:09:22

○MXaspmx3.googlemail.com2019-03-28 → 2019-03-28 · 4 obs

○ 2017-02-12 23:31:54
● 2019-03-28 22:51:36
○ 2026-02-19 18:20:34
○ 2026-03-24 22:09:22

○MXmail.b-io.co2016-06-26 → 2017-02-12 · 5 obs

○ 2016-02-27 10:57:44
● 2016-06-26 15:01:48
● 2017-02-12 23:31:54
○ 2019-03-28 22:51:36
○ 2026-03-24 22:09:22

○MXp.nsm.ctmail.com2016-02-27 → 2016-02-27 · 3 obs

● 2016-02-27 10:57:44
○ 2016-06-26 15:01:48
○ 2026-03-24 22:09:22

●MXsilverbells-com.mail.protection.outlook.com2026-02-19 → 2026-03-24 · 3 obs

○ 2019-03-28 22:51:36
● 2026-02-19 18:20:34
● 2026-03-24 22:09:22

○MXsilverbells.com2019-03-28 → 2019-03-28 · 4 obs

○ 2017-02-12 23:31:54
● 2019-03-28 22:51:36
○ 2026-02-19 18:20:34
○ 2026-03-24 22:09:22

●A104.21.60.1262026-02-19 → 2026-03-24 · 3 obs

○ 2019-03-28 22:51:36
● 2026-02-19 18:20:34
● 2026-03-24 22:09:22

●A172.67.196.1582026-02-19 → 2026-03-24 · 3 obs

○ 2019-03-28 22:51:36
● 2026-02-19 18:20:34
● 2026-03-24 22:09:22

○A192.154.225.572019-03-28 → 2019-03-28 · 4 obs

○ 2017-02-12 23:31:54
● 2019-03-28 22:51:36
○ 2026-02-19 18:20:34
○ 2026-03-24 22:09:22

○A192.155.81.1042016-06-26 → 2017-02-12 · 5 obs

○ 2016-02-27 10:57:44
● 2016-06-26 15:01:48
● 2017-02-12 23:31:54
○ 2019-03-28 22:51:36
○ 2026-03-24 22:09:22

○A199.59.243.1202015-07-11 → 2015-11-19 · 5 obs

○ 2007-11-01 00:08:26
● 2015-07-11 19:06:54
● 2015-11-19 09:27:32
○ 2016-02-27 10:57:44
○ 2026-03-24 22:09:22

●A2606:4700:3031::ac43:c49e2026-02-19 → 2026-03-24 · 3 obs

○ 2019-03-28 22:51:36
● 2026-02-19 18:20:34
● 2026-03-24 22:09:22

●A2606:4700:3032::6815:3c7e2026-02-19 → 2026-03-24 · 3 obs

○ 2019-03-28 22:51:36
● 2026-02-19 18:20:34
● 2026-03-24 22:09:22

○A64.14.244.602007-11-01 → 2007-11-01 · 3 obs

● 2007-11-01 00:08:26
○ 2015-07-11 19:06:54
○ 2026-03-24 22:09:22

○A64.34.46.602007-11-01 → 2007-11-01 · 3 obs

● 2007-11-01 00:08:26
○ 2015-07-11 19:06:54
○ 2026-03-24 22:09:22

○A69.64.147.2432016-02-27 → 2016-02-27 · 4 obs

○ 2015-11-19 09:27:32
● 2016-02-27 10:57:44
○ 2016-06-26 15:01:48
○ 2026-03-24 22:09:22

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
silverbells.com	ivan.ns.cloudflare.com, gwen.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:108.162.193.120

NS records: ivan.ns.cloudflare.com, gwen.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for silverbells.com (unsigned zone)

⏱️ Timing

Total: 161ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`172.67.196.158, 104.21.60.126`
AAAA	2	`2606:4700:3032::6815:3c7e, 2606:4700:3031::ac43:c49e`
NS	2	`gwen.ns.cloudflare.com, ivan.ns.cloudflare.com`
MX	1	`silverbells-com.mail.protection.outlook.`
TXT	3	`MS=ms57520339, google-site-verification=ez9UxcCYDB-V-8z...`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`gwen.ns.cloudflare.com dns.cloudflare.co`

📌 Glue Records Collected

Total: 12

Out-of-bailiwick: 12 (ivan.ns.cloudflare.com, ivan.ns.cloudflare.com, ivan.ns.cloudflare.com...)

Analysis

IP Addresses

silverbells.com refers to four IP numbers: 2606:4700:3031::ac43:c49e, 2606:4700:3032::6815:3c7e, 104.21.60.126 and 172.67.196.158.

Other host names, for instance www.coinbet24.com, estacaolanche.com.br, ycxfsx.com, barracudalpt.com and a14ec3fb840b.kvitka212.com.ua share IP numbers with silverbells.com.

Name Servers

silverbells.com's delegation uses two name servers: gwen.ns.cloudflare.com and ivan.ns.cloudflare.com.

silverbells.com uses the same name server setup as other domains, such as nri-na.com, dkonieczek.com, americasbestfranchises.com, channuoiheo.com and blueridgemediacompany.com.

silverbells.com at least partially shares name servers with other domains, including peterdalmaris.com, henrikstorner.dk, killerfm.com, kadinpemkobitung.org and gboil.com.

These name servers are commonly used with chip.ns.cloudflare.com, theo.ns.cloudflare.com and bryce.ns.cloudflare.com.

Host names with six IP numbers:

gwen.ns.cloudflare.com points to 2606:4700:50::adf5:3aa0, 2803:f800:50::6ca2:c0a0, 2a06:98c1:50::ac40:20a0, 108.162.192.160, 172.64.32.160 and 173.245.58.160.

ivan.ns.cloudflare.com points to 2606:4700:58::adf5:3b78, 2803:f800:50::6ca2:c178, 2a06:98c1:50::ac40:2178, 108.162.193.120, 172.64.33.120 and 173.245.59.120.

Mail Servers

A single mail server handles silverbells.com, silverbells-com.mail.protection.outlook.com.

Host silverbells-com.mail.protection.outlook.com points to eight IPs: 2a01:111:f403:c91d::a, 2a01:111:f403:c936::, 2a01:111:f403:c946::7, 2a01:111:f403:f912::, 52.101.9.0, 52.101.9.14, 52.101.10.6 and 52.101.11.13.

silverbells.com - robtex.com

silverbells.com

com

Previously MX for

Same first word

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

📌 Glue Records Collected

Analysis

IP Addresses

Name Servers

Mail Servers

`silverbells.com`

`com`