`brighamservices.com`

DNSSEC	⚠️ Not signed
A	3.220.225.62^{🇺🇸 Amazon3.208.0.0/12 EC2 IAD prefix}
		PTR	`ec2-3-220-225-62.compute-1.amazonaws.com`
A	3.225.142.148^{🇺🇸 Amazon3.224.0.0/12 EC2 IAD prefix}
A	52.5.206.218^{🇺🇸 Amazon52.4.0.0/14 EC2 IAD prefix}
NS	`ns-1300.awsdns-34.org` ⭐ ⚠️ Not in parent delegation
		A	2600:9000:5305:1400::1^{🇺🇸 Amazon2600:9000:5305::/48 - CloudFront}
			PTR	`ns-1300.awsdns-34.org`
		A	205.251.197.20^{🇺🇸 Amazon205.251.197.0/24 prefix}
			PTR	`ns-1300.awsdns-34.org`
NS	`ns-1635.awsdns-12.co.uk` ⚠️ Not in parent delegation
		A	2600:9000:5306:6300::1^{🇺🇸 Amazon2600:9000:5306::/48 - CloudFront}
			PTR	`ns-1635.awsdns-12.co.uk`
		A	205.251.198.99^{🇺🇸 Amazon205.251.198.0/24 prefix}
			PTR	`ns-1635.awsdns-12.co.uk`
NS	`ns-354.awsdns-44.com` ⚠️ Not in parent delegation
		A	2600:9000:5301:6200::1^{🇺🇸 Amazon2600:9000:5301::/48 - CloudFront}
			PTR	`ns-354.awsdns-44.com`
		A	205.251.193.98^{🇺🇸 Amazon205.251.193.0/24 prefix}
			PTR	`ns-354.awsdns-44.com`
NS	`ns-536.awsdns-03.net` ⚠️ Not in parent delegation
		A	2600:9000:5302:1800::1^{🇺🇸 Amazon2600:9000:5302::/48 - CloudFront}
			PTR	`ns-536.awsdns-03.net`
		A	205.251.194.24^{🇺🇸 Amazon205.251.194.0/24 prefix}
			PTR	`ns-536.awsdns-03.net`
NS	`ns1.getnetset.com` ⚠️ Not in zone NS records
		A	2600:9000:5305:1400::1^{🇺🇸 Amazon2600:9000:5305::/48 - CloudFront}
			PTR	`ns-1300.awsdns-34.org`
		A	205.251.197.20^{🇺🇸 Amazon205.251.197.0/24 prefix}
			PTR	`ns-1300.awsdns-34.org`
NS	`ns2.getnetset.com` ⚠️ Not in zone NS records
		A	2600:9000:5306:6300::1^{🇺🇸 Amazon2600:9000:5306::/48 - CloudFront}
			PTR	`ns-1635.awsdns-12.co.uk`
		A	205.251.198.99^{🇺🇸 Amazon205.251.198.0/24 prefix}
			PTR	`ns-1635.awsdns-12.co.uk`
NS	`ns3.getnetset.com` ⚠️ Not in zone NS records
		A	2600:9000:5301:6200::1^{🇺🇸 Amazon2600:9000:5301::/48 - CloudFront}
			PTR	`ns-354.awsdns-44.com`
		A	205.251.193.98^{🇺🇸 Amazon205.251.193.0/24 prefix}
			PTR	`ns-354.awsdns-44.com`
NS	`ns4.getnetset.com` ⚠️ Not in zone NS records
		A	2600:9000:5302:1800::1^{🇺🇸 Amazon2600:9000:5302::/48 - CloudFront}
			PTR	`ns-536.awsdns-03.net`
		A	205.251.194.24^{🇺🇸 Amazon205.251.194.0/24 prefix}
			PTR	`ns-536.awsdns-03.net`
MX	`brighamservices-com.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c902::16^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-byapr04cu00306.inbound.protection.outlook.com`
		A	2a01:111:f403:f901::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-mn2pr04cu00200.inbound.protection.outlook.com`
		A	2a01:111:f403:f90d::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sn1pr0501cu00301.inbound.protection.outlook.com`
		A	2a01:111:f403:f910::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-cy5pr03cu00300.inbound.protection.outlook.com`
		A	52.101.9.17^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`ip-52-101-9-17.defastlink.net`
		A	52.101.10.6^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bn1pr21cu00106.inbound.protection.outlook.com`
		A	52.101.11.3^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sn1pr0501cu00103.inbound.protection.outlook.com`
		A	52.101.41.56^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sj0pr21cu00100.inbound.protection.outlook.com`
TXT	`MS=ms57023898`
TXT	`v=spf1 include:spf.protection.outlook.com -all`
SOA	`ns-1300.awsdns-34.org`awsdns-hostmaster@amazon.com 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=1771291435

DNS History

17 records (12 active, 5 former)

●NSns-1300.awsdns-34.org2026-03-15 → 2026-03-15 · 3 obs

○ 2018-07-06 04:56:58
● 2026-03-15 09:41:46
● 2026-03-15 09:41:50

●NSns-1635.awsdns-12.co.uk2026-03-15 → 2026-03-15 · 3 obs

○ 2018-07-06 04:56:58
● 2026-03-15 09:41:46
● 2026-03-15 09:41:50

●NSns-354.awsdns-44.com2026-03-15 → 2026-03-15 · 3 obs

○ 2018-07-06 04:56:58
● 2026-03-15 09:41:46
● 2026-03-15 09:41:50

●NSns-536.awsdns-03.net2026-03-15 → 2026-03-15 · 3 obs

○ 2018-07-06 04:56:58
● 2026-03-15 09:41:46
● 2026-03-15 09:41:50

●NSns1.getnetset.com2026-03-15 → 2026-03-15 · 3 obs

○ 2018-07-06 04:56:58
● 2026-03-15 09:41:46
● 2026-03-15 09:41:50

○NSns19.domaincontrol.com2015-07-10 → 2018-07-06 · 4 obs

● 2015-07-10 15:15:00
● 2018-07-06 04:56:58
○ 2026-03-15 09:41:46
○ 2026-03-15 09:41:50

●NSns2.getnetset.com2026-03-15 → 2026-03-15 · 3 obs

○ 2018-07-06 04:56:58
● 2026-03-15 09:41:46
● 2026-03-15 09:41:50

○NSns20.domaincontrol.com2015-07-10 → 2018-07-06 · 4 obs

● 2015-07-10 15:15:00
● 2018-07-06 04:56:58
○ 2026-03-15 09:41:46
○ 2026-03-15 09:41:50

●NSns3.getnetset.com2026-03-15 → 2026-03-15 · 3 obs

○ 2018-07-06 04:56:58
● 2026-03-15 09:41:46
● 2026-03-15 09:41:50

●NSns4.getnetset.com2026-03-15 → 2026-03-15 · 3 obs

○ 2018-07-06 04:56:58
● 2026-03-15 09:41:46
● 2026-03-15 09:41:50

●MXbrighamservices-com.mail.protection.outlook.com2018-07-06 → 2026-03-15 · 3 obs

○ 2017-01-16 12:15:26
● 2018-07-06 04:56:58
● 2026-03-15 09:41:50

○MXmailstore1.secureserver.net2015-07-10 → 2017-01-16 · 4 obs

● 2015-07-10 15:15:00
● 2017-01-16 12:15:26
○ 2018-07-06 04:56:58
○ 2026-03-15 09:41:50

○MXsmtp.secureserver.net2015-07-10 → 2017-01-16 · 4 obs

● 2015-07-10 15:15:00
● 2017-01-16 12:15:26
○ 2018-07-06 04:56:58
○ 2026-03-15 09:41:50

●A3.220.225.622026-03-15 → 2026-03-15 · 3 obs

○ 2018-07-06 04:56:58
● 2026-03-15 09:41:46
● 2026-03-15 09:41:50

●A3.225.142.1482026-03-15 → 2026-03-15 · 3 obs

○ 2018-07-06 04:56:58
● 2026-03-15 09:41:46
● 2026-03-15 09:41:50

○A50.63.202.132015-07-10 → 2018-07-06 · 4 obs

● 2015-07-10 15:15:00
● 2018-07-06 04:56:58
○ 2026-03-15 09:41:46
○ 2026-03-15 09:41:50

●A52.5.206.2182026-03-15 → 2026-03-15 · 3 obs

○ 2018-07-06 04:56:58
● 2026-03-15 09:41:46
● 2026-03-15 09:41:50

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, f.gtld-servers.net, l.gtld-servers.net, j.gtld-servers.net...	-
brighamservices.com	ns1.getnetset.com, ns2.getnetset.com, ns3.getnetset.com, ns4.getnetset.com	8 records

✅ Authoritative Response

Server: 205.251.194.24

NS records: ns1.getnetset.com, ns2.getnetset.com, ns3.getnetset.com, ns4.getnetset.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for brighamservices.com (unsigned zone)

⏱️ Timing

Total: 1144ms | Queries: -

📄 Records

Type	Count	Sample Data
A	3	`52.5.206.218, 3.220.225.62...`
NS	4	`ns-1300.awsdns-34.org, ns-1635.awsdns-12.co.uk...`
MX	1	`brighamservices-com.mail.protection.outl`
TXT	2	`MS=ms57023898, v=spf1 include:spf.protection.outlook.co`
SOA	1	`ns-1300.awsdns-34.org awsdns-hostmaster.`

📌 Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (ns1.getnetset.com, ns1.getnetset.com, ns2.getnetset.com...)

Analysis

IP Addresses

brighamservices.com points to IPs: 3.220.225.62, 3.225.142.148 and 52.5.206.218.

Other host names, for instance moneywisetax.com, rosegcpa.com, brennercpas.com, fortunatefields.com and taxwise-cpa.com share IP numbers with brighamservices.com.

Name Servers

Eight name servers are delegated to brighamservices.com: ns-354.awsdns-44.com, ns1.getnetset.com, ns2.getnetset.com, ns3.getnetset.com, ns4.getnetset.com, ns-536.awsdns-03.net, ns-1300.awsdns-34.org and ns-1635.awsdns-12.co.uk.

brighamservices.com at least partially shares name servers with other domains such as betterfitness.net, cruiseservice.com.br, educecloud.com, tele-coffee.com and d169vhnrswyxft.cloudfront.net.

These name servers are commonly used alongside ns-63.awsdns-07.com, ns-771.awsdns-32.net and ns-1579.awsdns-05.co.uk.

Hostnames with two IPs

ns-354.awsdns-44.com points to: 2600:9000:5301:6200::1 and 205.251.193.98.

ns1.getnetset.com points to: 2600:9000:5305:1400::1 and 205.251.197.20.

ns2.getnetset.com points to: 2600:9000:5306:6300::1 and 205.251.198.99.

ns3.getnetset.com points to: 2600:9000:5301:6200::1 and 205.251.193.98.

ns4.getnetset.com points to: 2600:9000:5302:1800::1 and 205.251.194.24.

ns-536.awsdns-03.net points to: 2600:9000:5302:1800::1 and 205.251.194.24.

ns-1300.awsdns-34.org points to: 2600:9000:5305:1400::1 and 205.251.197.20.

ns-1635.awsdns-12.co.uk points to: 2600:9000:5306:6300::1 and 205.251.198.99.

Hostnames that point to 2600:9000:5301:6200::1: ns-354.awsdns-44.com and ns3.getnetset.com.

Hostnames that point to 205.251.193.98: ns-354.awsdns-44.com and ns3.getnetset.com.

Hostnames that point to 2600:9000:5305:1400::1: ns1.getnetset.com and ns-1300.awsdns-34.org.

Hostnames that point to 205.251.197.20: ns1.getnetset.com and ns-1300.awsdns-34.org.

Hostnames that point to 2600:9000:5306:6300::1: ns2.getnetset.com and ns-1635.awsdns-12.co.uk.

Hostnames that point to 205.251.198.99: ns2.getnetset.com and ns-1635.awsdns-12.co.uk.

Hostnames that point to 2600:9000:5302:1800::1: ns4.getnetset.com and ns-536.awsdns-03.net.

Hostnames that point to 205.251.194.24: ns4.getnetset.com and ns-536.awsdns-03.net.

Mail Servers

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

brighamservices-com.mail.protection.outlook.com points to eight IP numbers: 2a01:111:f403:c902::16, 2a01:111:f403:f901::, 2a01:111:f403:f90d::1, 2a01:111:f403:f910::, 52.101.9.17, 52.101.10.6, 52.101.11.3 and 52.101.41.56.

brighamservices.com - robtex.com