`technologyforce.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` ⭐ ⚠️ Not in parent delegation
		A	64.202.240.106^{🇺🇸 USINTERNET64.202.240.0/21 Mainstream}
NS	`ns1.technologyforce.com` ⚠️ Not in zone NS records
		A	64.202.240.106^{🇺🇸 USINTERNET64.202.240.0/21 Mainstream}
NS	`ns2.belayhost.com` ⚠️ Not in parent delegation
		A	46.202.92.19^{🇺🇦 IIHOS00146.202.88.0/21 HOSTINGER US}
			PTR	`srv642334.hstgr.cloud`
NS	`ns2.technologyforce.com` ⚠️ Not in zone NS records
		A	46.202.92.19^{🇺🇦 IIHOS00146.202.88.0/21 HOSTINGER US}
			PTR	`srv642334.hstgr.cloud`
NS	`ns3.belayhost.com` ⚠️ Not in parent delegation
		A	64.202.240.105^{🇺🇸 USINTERNET64.202.240.0/21 Mainstream}
MX	`d314464a.ess.barracudanetworks.com` ⭐
		A	209.222.82.252^{🇺🇸 Amazon209.222.82.0/24 EC2 Prefix}
			PTR	`mail.ess.barracuda.com`
		A	209.222.82.253^{🇺🇸 Amazon209.222.82.0/24 EC2 Prefix}
			PTR	`mail.ess.barracuda.com`
		A	209.222.82.255^{🇺🇸 Amazon209.222.82.0/24 EC2 Prefix}
			PTR	`mail.ess.barracuda.com`
MX	`d314464b.ess.barracudanetworks.com`⁽²⁰⁾
		A	209.222.82.252^{🇺🇸 Amazon209.222.82.0/24 EC2 Prefix}
			PTR	`mail.ess.barracuda.com`
		A	209.222.82.253^{🇺🇸 Amazon209.222.82.0/24 EC2 Prefix}
			PTR	`mail.ess.barracuda.com`
		A	209.222.82.255^{🇺🇸 Amazon209.222.82.0/24 EC2 Prefix}
			PTR	`mail.ess.barracuda.com`
TXT	`v=spf1 ip4:167.88.45.5 include:spf.protection.outlook.com ~all`
TXT	`MS=ms34961230`
TXT	`google-site-verification=PRdCLrJXBz2Q2zthnfw11Lsj4qpkLczbfOcrNzYhJVo`
TXT	`google-site-verification=UNns9lwsJhi0jPvjU0PhAeBh6XqYrz6Y0ScUcQAwMfw`
SOA	`ns1.belayhost.com`kent@belayhost.com 2026-06-04 #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=1784734112

Subdomains

ns2.technologyforce.com

mail.technologyforce.com

ns1.technologyforce.com

Same first word

technologyforce.com

Similar names

forcetechnology.se

forcetechnology.no

forcetechnology.us

forcetechnology.sg

forcetechnology.com

forcetechnology.cn

forcetechnology.dk

forcetechnology.com.au

DNS History

18 records (9 active, 9 former)

●NSns1.belayhost.com2015-11-28 → 2026-07-22 · 3 obs

○ 2015-08-19 14:16:18
● 2015-11-28 12:54:08
● 2026-07-22 15:43:52

○NSns1.sunservernetworks.com2007-08-13 → 2007-08-13 · 3 obs

● 2007-08-13 11:15:40
○ 2015-08-19 14:16:18
○ 2026-07-22 15:43:52

●NSns1.technologyforce.com2015-08-19 → 2026-07-22 · 6 obs

○ 2007-08-13 11:15:40
● 2015-08-19 14:16:18
○ 2015-11-28 12:54:08
○ 2017-02-19 11:59:16
● 2026-02-16 10:15:42
● 2026-07-22 15:43:52

●NSns2.belayhost.com2015-11-28 → 2026-07-22 · 3 obs

○ 2015-08-19 14:16:18
● 2015-11-28 12:54:08
● 2026-07-22 15:43:52

○NSns2.sunserver.com2007-08-13 → 2007-08-13 · 3 obs

● 2007-08-13 11:15:40
○ 2015-08-19 14:16:18
○ 2026-07-22 15:43:52

●NSns2.technologyforce.com2015-08-19 → 2026-07-22 · 6 obs

○ 2007-08-13 11:15:40
● 2015-08-19 14:16:18
○ 2015-11-28 12:54:08
○ 2017-02-19 11:59:16
● 2026-02-16 10:15:42
● 2026-07-22 15:43:52

●NSns3.belayhost.com2015-11-28 → 2026-07-22 · 3 obs

○ 2015-08-19 14:16:18
● 2015-11-28 12:54:08
● 2026-07-22 15:43:52

●MXd314464a.ess.barracudanetworks.com2026-02-16 → 2026-07-22 · 3 obs

○ 2017-02-19 11:59:16
● 2026-02-16 10:15:42
● 2026-07-22 15:43:52

●MXd314464b.ess.barracudanetworks.com2026-02-16 → 2026-07-22 · 3 obs

○ 2017-02-19 11:59:16
● 2026-02-16 10:15:42
● 2026-07-22 15:43:52

○MXeast.smtp.exch027.serverdata.net2015-08-19 → 2017-02-19 · 5 obs

○ 2007-08-13 11:15:40
● 2015-08-19 14:16:18
● 2017-02-19 11:59:16
○ 2026-02-16 10:15:42
○ 2026-07-22 15:43:52

○MXsmtp1.mke.securence.com2007-08-13 → 2007-08-13 · 3 obs

● 2007-08-13 11:15:40
○ 2015-08-19 14:16:18
○ 2026-07-22 15:43:52

○MXsmtp1.msp.securence.com2007-08-13 → 2007-08-13 · 3 obs

● 2007-08-13 11:15:40
○ 2015-08-19 14:16:18
○ 2026-07-22 15:43:52

○MXwest.smtp.exch027.serverdata.net2015-08-19 → 2017-02-19 · 5 obs

○ 2007-08-13 11:15:40
● 2015-08-19 14:16:18
● 2017-02-19 11:59:16
○ 2026-02-16 10:15:42
○ 2026-07-22 15:43:52

●A167.88.45.52026-02-16 → 2026-07-22 · 3 obs

○ 2017-02-19 11:59:16
● 2026-02-16 10:15:42
● 2026-07-22 15:43:52

○A209.240.72.492007-08-13 → 2007-08-13 · 3 obs

● 2007-08-13 11:15:40
○ 2015-08-19 14:16:18
○ 2026-07-22 15:43:52

●A2a02:4780:2d:c27a::12026-02-16 → 2026-07-22 · 3 obs

○ 2017-02-19 11:59:16
● 2026-02-16 10:15:42
● 2026-07-22 15:43:52

○A64.202.244.1192015-08-19 → 2015-08-19 · 4 obs

○ 2007-08-13 11:15:40
● 2015-08-19 14:16:18
○ 2015-11-28 12:54:08
○ 2026-07-22 15:43:52

○A64.202.249.312015-11-28 → 2017-02-19 · 5 obs

○ 2015-08-19 14:16:18
● 2015-11-28 12:54:08
● 2017-02-19 11:59:16
○ 2026-02-16 10:15:42
○ 2026-07-22 15:43:52

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
technologyforce.com	ns1.technologyforce.com, ns2.technologyforce.com	2 records

✅ Authoritative Response

Server:64.202.240.106

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for technologyforce.com (unsigned zone)

⏱️ Timing

Total: 1580ms | 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	2	`d314464b.ess.barracudanetworks.com (pri:, d314464a.ess.barracudanetworks.com (pri:`
TXT	4	`v=spf1 ip4:167.88.45.5 include:spf.prote, MS=ms34961230...`
SOA	1	`ns1.belayhost.com kent.belayhost.com`

📌 Glue Records Collected

Total: 2

In-bailiwick: 2 (ns1.technologyforce.com, ns2.technologyforce.com)

Analysis

Hierarchy

technologyforce.com sits above ns2.technologyforce.com, mail.technologyforce.com and ns1.technologyforce.com in the domain hierarchy.

IP Addresses

technologyforce.com points to the IP addresses 167.88.45.5 and 2a02:4780:2d:c27a::1

Additional host names — mirman.net, mcg.net, constructionconsultinggroup.com and two others — share IP numbers with technologyforce.com.

Name Servers

Delegation for technologyforce.com is to five name servers: ns1.belayhost.com, ns2.belayhost.com, ns3.belayhost.com and two others.

There is at least partial name server overlap between technologyforce.com and other domains — mayermn.gov, mainsol.net, datalogics.net and two more among them.

These name servers frequently co-occur with the name servers ns2.mcg.net and ns.mcg.net.

Host names pointing to a single IP address:

ns1.belayhost.com resolves to 64.202.240.106.

ns2.belayhost.com resolves to 46.202.92.19.

ns3.belayhost.com resolves to 64.202.240.105.

ns1.technologyforce.com resolves to 64.202.240.106.

ns2.technologyforce.com resolves to 46.202.92.19.

The host names ns1.belayhost.com and ns1.technologyforce.com both resolve to 64.202.240.106 IP addresses.

The host names ns2.belayhost.com and ns2.technologyforce.com both resolve to 46.202.92.19 IP addresses.

Mail Servers

technologyforce.com has two mail servers: d314464a.ess.barracudanetworks.com and d314464b.ess.barracudanetworks.com.

Both d314464a.ess.barracudanetworks.com and d314464b.ess.barracudanetworks.com point to the same three IP addresses: 209.222.82.252, 209.222.82.253 and 209.222.82.255.

The host names d314464a.ess.barracudanetworks.com and d314464b.ess.barracudanetworks.com both resolve to 209.222.82.252 IP addresses.

The host names d314464a.ess.barracudanetworks.com and d314464b.ess.barracudanetworks.com both resolve to 209.222.82.253 IP addresses.

The host names d314464a.ess.barracudanetworks.com and d314464b.ess.barracudanetworks.com both resolve to 209.222.82.255 IP addresses.

technologyforce.com - robtex.com