haloconnect.com - dns.ninja

`haloconnect.com`

DNSSEC	⚠️ Not signed
NS	`ns-1566.awsdns-03.co.uk` ⭐
		A	2600:9000:5306:1e00::1^{🇺🇸 Amazon2600:9000:5306::/48 - CloudFront}
			PTR	`ns-1566.awsdns-03.co.uk`
		A	205.251.198.30^{🇺🇸 Amazon205.251.198.0/24 prefix}
			PTR	`ns-1566.awsdns-03.co.uk`
NS	`ns-1197.awsdns-21.org`
		A	2600:9000:5304:ad00::1^{🇺🇸 Amazon2600:9000:5304::/48 - CloudFront}
			PTR	`ns-1197.awsdns-21.org`
		A	205.251.196.173^{🇺🇸 Amazon205.251.196.0/24 prefix}
			PTR	`ns-1197.awsdns-21.org`
NS	`ns-19.awsdns-02.com`
		A	2600:9000:5300:1300::1^{🇺🇸 Amazon2600:9000:5300::/48 - CloudFront}
			PTR	`ns-19.awsdns-02.com`
		A	205.251.192.19^{🇺🇸 Amazon205.251.192.0/24 prefix}
			PTR	`ns-19.awsdns-02.com`
NS	`ns-905.awsdns-49.net`
		A	2600:9000:5303:8900::1^{🇺🇸 Amazon2600:9000:5303::/48 - CloudFront}
			PTR	`ns-905.awsdns-49.net`
		A	205.251.195.137^{🇺🇸 Amazon205.251.195.0/24 prefix}
			PTR	`ns-905.awsdns-49.net`
MX	`inbound-smtp.us-west-2.amazonaws.com` ⭐
		A	35.161.157.106^{🇺🇸 Amazon35.160.0.0/13 EC2 PDX prefix}
			PTR	`ec2-35-161-157-106.us-west-2.compute.amazonaws.com`
		A	52.13.163.116^{🇺🇸 Amazon52.12.0.0/15 EC2 PDX prefix}
			PTR	`ec2-52-13-163-116.us-west-2.compute.amazonaws.com`
		A	52.43.162.244^{🇺🇸 Amazon52.40.0.0/14 EC2 PDX prefix}
			PTR	`ec2-52-43-162-244.us-west-2.compute.amazonaws.com`
		A	54.188.121.70^{🇺🇸 Amazon54.188.0.0/15 EC2 PDX prefix}
			PTR	`ec2-54-188-121-70.us-west-2.compute.amazonaws.com`
SOA	`ns-1566.awsdns-03.co.uk`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=1780545139

Same first word

haloconnect.com

haloconnect.io

Similar names

holaconnect.com

DNS History

25 records (5 active, 20 former)

○NSdns1.p03.nsone.net2017-02-17 → 2019-04-20 · 5 obs

○ 2016-06-28 15:02:32
● 2017-02-17 04:15:28
● 2019-04-20 17:43:40
○ 2026-02-23 17:56:32
○ 2026-06-04 03:55:34

○NSdns2.p03.nsone.net2017-02-17 → 2019-04-20 · 5 obs

○ 2016-06-28 15:02:32
● 2017-02-17 04:15:28
● 2019-04-20 17:43:40
○ 2026-02-23 17:56:32
○ 2026-06-04 03:55:34

○NSdns3.p03.nsone.net2017-02-17 → 2019-04-20 · 5 obs

○ 2016-06-28 15:02:32
● 2017-02-17 04:15:28
● 2019-04-20 17:43:40
○ 2026-02-23 17:56:32
○ 2026-06-04 03:55:34

○NSdns4.p03.nsone.net2017-02-17 → 2019-04-20 · 5 obs

○ 2016-06-28 15:02:32
● 2017-02-17 04:15:28
● 2019-04-20 17:43:40
○ 2026-02-23 17:56:32
○ 2026-06-04 03:55:34

●NSns-1197.awsdns-21.org2026-02-23 → 2026-06-04 · 3 obs

○ 2019-04-20 17:43:40
● 2026-02-23 17:56:32
● 2026-06-04 03:55:34

●NSns-1566.awsdns-03.co.uk2026-02-23 → 2026-06-04 · 3 obs

○ 2019-04-20 17:43:40
● 2026-02-23 17:56:32
● 2026-06-04 03:55:34

●NSns-19.awsdns-02.com2026-02-23 → 2026-06-04 · 3 obs

○ 2019-04-20 17:43:40
● 2026-02-23 17:56:32
● 2026-06-04 03:55:34

●NSns-905.awsdns-49.net2026-02-23 → 2026-06-04 · 3 obs

○ 2019-04-20 17:43:40
● 2026-02-23 17:56:32
● 2026-06-04 03:55:34

○NSns01.squarespacedns.com2019-04-20 → 2019-04-20 · 4 obs

○ 2017-02-17 04:15:28
● 2019-04-20 17:43:40
○ 2026-02-23 17:56:32
○ 2026-06-04 03:55:34

○NSns02.squarespacedns.com2019-04-20 → 2019-04-20 · 4 obs

○ 2017-02-17 04:15:28
● 2019-04-20 17:43:40
○ 2026-02-23 17:56:32
○ 2026-06-04 03:55:34

○NSns03.squarespacedns.com2019-04-20 → 2019-04-20 · 4 obs

○ 2017-02-17 04:15:28
● 2019-04-20 17:43:40
○ 2026-02-23 17:56:32
○ 2026-06-04 03:55:34

○NSns04.squarespacedns.com2019-04-20 → 2019-04-20 · 4 obs

○ 2017-02-17 04:15:28
● 2019-04-20 17:43:40
○ 2026-02-23 17:56:32
○ 2026-06-04 03:55:34

○NSns1.systemdns.com2016-06-28 → 2016-06-28 · 4 obs

○ 2016-03-08 23:15:22
● 2016-06-28 15:02:32
○ 2017-02-17 04:15:28
○ 2026-06-04 03:55:34

○NSns2.systemdns.com2016-06-28 → 2016-06-28 · 4 obs

○ 2016-03-08 23:15:22
● 2016-06-28 15:02:32
○ 2017-02-17 04:15:28
○ 2026-06-04 03:55:34

○NSns3.systemdns.com2016-06-28 → 2016-06-28 · 4 obs

○ 2016-03-08 23:15:22
● 2016-06-28 15:02:32
○ 2017-02-17 04:15:28
○ 2026-06-04 03:55:34

○NSns71.domaincontrol.com2015-08-18 → 2016-03-08 · 4 obs

● 2015-08-18 21:05:34
● 2016-03-08 23:15:22
○ 2016-06-28 15:02:32
○ 2026-06-04 03:55:34

○NSns72.domaincontrol.com2015-08-18 → 2016-03-08 · 4 obs

● 2015-08-18 21:05:34
● 2016-03-08 23:15:22
○ 2016-06-28 15:02:32
○ 2026-06-04 03:55:34

●MXinbound-smtp.us-west-2.amazonaws.com2026-02-23 → 2026-06-04 · 3 obs

○ 2016-06-28 15:02:32
● 2026-02-23 17:56:32
● 2026-06-04 03:55:34

○MXmailstore1.secureserver.net2015-08-18 → 2016-03-08 · 4 obs

● 2015-08-18 21:05:34
● 2016-03-08 23:15:22
○ 2016-06-28 15:02:32
○ 2026-06-04 03:55:34

○MXsmtp.secureserver.net2015-08-18 → 2016-03-08 · 4 obs

● 2015-08-18 21:05:34
● 2016-03-08 23:15:22
○ 2016-06-28 15:02:32
○ 2026-06-04 03:55:34

○A198.185.159.1442017-02-17 → 2019-04-20 · 5 obs

○ 2016-06-28 15:02:32
● 2017-02-17 04:15:28
● 2019-04-20 17:43:40
○ 2026-02-23 17:56:32
○ 2026-06-04 03:55:34

○A198.185.159.1452017-02-17 → 2019-04-20 · 5 obs

○ 2016-06-28 15:02:32
● 2017-02-17 04:15:28
● 2019-04-20 17:43:40
○ 2026-02-23 17:56:32
○ 2026-06-04 03:55:34

○A198.49.23.1442017-02-17 → 2019-04-20 · 5 obs

○ 2016-06-28 15:02:32
● 2017-02-17 04:15:28
● 2019-04-20 17:43:40
○ 2026-02-23 17:56:32
○ 2026-06-04 03:55:34

○A198.49.23.1452016-06-28 → 2019-04-20 · 5 obs

○ 2016-03-08 23:15:22
● 2016-06-28 15:02:32
● 2019-04-20 17:43:40
○ 2026-02-23 17:56:32
○ 2026-06-04 03:55:34

○A50.63.202.472015-08-18 → 2016-03-08 · 4 obs

● 2015-08-18 21:05:34
● 2016-03-08 23:15:22
○ 2016-06-28 15:02:32
○ 2026-06-04 03:55:34

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	k.gtld-servers.net, c.gtld-servers.net, e.gtld-servers.net, m.gtld-servers.net...	-
haloconnect.com	ns-19.awsdns-02.com, ns-905.awsdns-49.net, ns-1566.awsdns-03.co.uk, ns-1197.awsdns-21.org	2 records

✅ Authoritative Response

Server:205.251.198.30

NS records: ns-19.awsdns-02.com, ns-905.awsdns-49.net, ns-1566.awsdns-03.co.uk, ns-1197.awsdns-21.org

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for haloconnect.com (unsigned zone)

⏱️ Timing

Total: 502ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns-1197.awsdns-21.org, ns-1566.awsdns-03.co.uk...`
MX	1	`inbound-smtp.us-west-2.amazonaws.com (pr`
SOA	1	`ns-1566.awsdns-03.co.uk awsdns-hostmaste`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns-19.awsdns-02.com, ns-19.awsdns-02.com)

Analysis

Name Servers

The DNS delegation for haloconnect.com covers 4 name servers — ns-19.awsdns-02.com, ns-905.awsdns-49.net, ns-1197.awsdns-21.org and ns-1566.awsdns-03.co.uk.

All four hostnames — ns-19.awsdns-02.com, ns-905.awsdns-49.net, ns-1197.awsdns-21.org and ns-1566.awsdns-03.co.uk — resolve to two IP numbers apiece: ns-19.awsdns-02.com to 205.251.192.19 and 2600:9000:5300:1300::1; ns-905.awsdns-49.net to 205.251.195.137 and 2600:9000:5303:8900::1; ns-1197.awsdns-21.org to 205.251.196.173 and 2600:9000:5304:ad00::1; ns-1566.awsdns-03.co.uk to 205.251.198.30 and 2600:9000:5306:1e00::1.

Mail Servers

Mail for haloconnect.com is handled by a single mail server, inbound-smtp.us-west-2.amazonaws.com.

haloconnect.com has at least partial mail server overlap with other domains such as supplier.awsapps.com, vuics.com, f1scope.com and two more.

These mail servers are often used together with the mail servers inbound-smtp.us-east-1.amazonaws.com, aspmx.l.google.com, alt1.aspmx.l.google.com and alt2.aspmx.l.google.com.

With 4 IP numbers, inbound-smtp.us-west-2.amazonaws.com resolves to 35.161.157.106, 52.13.163.116, 52.43.162.244 and 54.188.121.70.