`brandnetworking.com`

DNSSEC	⚠️ Not signed
A	2a02:4780:2d:c27a::1^{🇨🇾 IIHOS0012a02:4780:2d::/48 HOSTINGER US}
		PTR	`srv663902.hstgr.cloud`
A	167.88.45.5^{🇨🇦 IIHOS001167.88.40.0/21 HOSTINGER US}
NS	`ns1.belayhost.com` ⭐
		A	64.202.240.103^{🇺🇸 USINTERNET64.202.240.0/21 Mainstream}
NS	`ns2.belayhost.com`
		A	46.202.92.19^{🇺🇦 IIHOS00146.202.88.0/21 HOSTINGER US}
			PTR	`srv642334.hstgr.cloud`
NS	`ns3.belayhost.com`
		A	64.202.240.105^{🇺🇸 USINTERNET64.202.240.0/21 Mainstream}
MX	`brandnetworking-com.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c902::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sj2pr05cu00401.inbound.protection.outlook.com`
		A	2a01:111:f403:c903::3^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-mw2pr02cu00503.inbound.protection.outlook.com`
		A	2a01:111:f403:c92c::4^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-dm6pr05cu00404.inbound.protection.outlook.com`
		A	2a01:111:f403:f905::4^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-dm2pr04cu00404.inbound.protection.outlook.com`
		A	52.101.11.7^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sa9pr04cu00107.inbound.protection.outlook.com`
		A	52.101.40.2^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-cy1pr05cu00402.inbound.protection.outlook.com`
		A	52.101.41.28^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sj0pr03cu01504.inbound.protection.outlook.com`
		A	52.101.41.183^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-byapr04cu00307.inbound.protection.outlook.com`
TXT	`v=spf1 a mx include:spf.protection.outlook.com -all`
SOA	`ns1.belayhost.com`kent@belayhost.com 2026-04-10 #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=1777482431

Same first word

brandnetworking.com

DNS History

12 records (6 active, 6 former)

○NSns.mcg.net2015-05-25 → 2017-03-31 · 4 obs

● 2015-05-25 18:06:16
● 2017-03-31 09:45:58
○ 2026-04-04 11:16:36
○ 2026-04-29 17:21:00

●NSns1.belayhost.com2026-04-04 → 2026-04-29 · 3 obs

○ 2017-03-31 09:45:58
● 2026-04-04 11:16:36
● 2026-04-29 17:21:00

●NSns2.belayhost.com2026-04-04 → 2026-04-29 · 3 obs

○ 2017-03-31 09:45:58
● 2026-04-04 11:16:36
● 2026-04-29 17:21:00

○NSns2.mcg.net2015-05-25 → 2017-03-31 · 4 obs

● 2015-05-25 18:06:16
● 2017-03-31 09:45:58
○ 2026-04-04 11:16:36
○ 2026-04-29 17:21:00

●NSns3.belayhost.com2026-04-04 → 2026-04-29 · 3 obs

○ 2017-03-31 09:45:58
● 2026-04-04 11:16:36
● 2026-04-29 17:21:00

●MXbrandnetworking-com.mail.protection.outlook.com2015-10-15 → 2026-04-29 · 3 obs

○ 2015-05-25 18:06:16
● 2015-10-15 00:19:14
● 2026-04-29 17:21:00

○MXsmtp1.mailserverfilter.com2015-05-25 → 2015-05-25 · 3 obs

● 2015-05-25 18:06:16
○ 2015-10-15 00:19:14
○ 2026-04-29 17:21:00

○MXsmtp2.mailserverfilter.com2015-05-25 → 2015-05-25 · 3 obs

● 2015-05-25 18:06:16
○ 2015-10-15 00:19:14
○ 2026-04-29 17:21:00

●A167.88.45.52026-04-04 → 2026-04-29 · 3 obs

○ 2017-03-31 09:45:58
● 2026-04-04 11:16:36
● 2026-04-29 17:21:00

●A2a02:4780:2d:c27a::12026-04-04 → 2026-04-29 · 3 obs

○ 2017-03-31 09:45:58
● 2026-04-04 11:16:36
● 2026-04-29 17:21:00

○A64.202.249.1002017-03-31 → 2017-03-31 · 4 obs

○ 2016-07-13 19:54:24
● 2017-03-31 09:45:58
○ 2026-04-04 11:16:36
○ 2026-04-29 17:21:00

○A64.202.249.202015-05-25 → 2016-07-13 · 4 obs

● 2015-05-25 18:06:16
● 2016-07-13 19:54:24
○ 2017-03-31 09:45:58
○ 2026-04-29 17:21:00

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	j.gtld-servers.net, l.gtld-servers.net, c.gtld-servers.net, b.gtld-servers.net...	-
brandnetworking.com	ns1.belayhost.com, ns2.belayhost.com, ns3.belayhost.com	3 records

✅ Authoritative Response

Server:64.202.240.103

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for brandnetworking.com (unsigned zone)

⏱️ Timing

Total: 803ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`167.88.45.5`
AAAA	1	`2a02:4780:2d:c27a::1`
NS	3	`ns3.belayhost.com, ns2.belayhost.com...`
MX	1	`brandnetworking-com.mail.protection.outl`
TXT	1	`v=spf1 a mx include:spf.protection.outlo`
SOA	1	`ns1.belayhost.com kent.belayhost.com`

📌 Glue Records Collected

Total: 3

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

Analysis

IP Addresses

brandnetworking.com resolves to two IP numbers: 2a02:4780:2d:c27a::1 and 167.88.45.5.

Other host names, for instance mcg.net, constructionconsultinggroup.com, belayhost.com, brand-corporation.com and heartwar.org share IP numbers with brandnetworking.com.

Name Servers

brandnetworking.com is delegated to three name servers: ns1.belayhost.com, ns2.belayhost.com and ns3.belayhost.com.

brandnetworking.com partially shares name servers with other domains; examples include redeeminglovechurch.com, mail.dymanykelectric.com, airiver.com, chrcom.net and mpii.com.

These name servers commonly accompany ns2.mcg.net, ns.mcg.net, ns1.technologyforce.com and ns2.technologyforce.com.

Host names with one IP number:

Host ns1.belayhost.com points to 64.202.240.103.

Host ns2.belayhost.com points to 46.202.92.19.

Host ns3.belayhost.com points to 64.202.240.105.

Mail Servers

brandnetworking.com is handled by a single mail server, brandnetworking-com.mail.protection.outlook.com.

Hostname brandnetworking-com.mail.protection.outlook.com points to eight IP numbers: 2a01:111:f403:c902::1, 2a01:111:f403:c903::3, 2a01:111:f403:c92c::4, 2a01:111:f403:f905::4, 52.101.11.7, 52.101.40.2, 52.101.41.28 and 52.101.41.183.

brandnetworking.com - robtex.com