`beacondigitals.com`

DNSSEC	⚠️ Not signed
A	192.250.227.243^{🇬🇧 WHG-DAL192.250.227.0/24}
		PTR	`s12772.usc1.stableserver.net`
NS	`ns1.us17.tmd.cloud` ⭐ ⚠️ Not in parent delegation
		A	13.248.158.180^{🇺🇸 Amazon13.248.144.0/20}
			PTR	`a79764cc55c0ac9c0.awsglobalaccelerator.com`
NS	`ns1.mysecurecloudhost.com` ⚠️ Not in zone NS records
		A	13.248.158.180^{🇺🇸 Amazon13.248.144.0/20}
			PTR	`a79764cc55c0ac9c0.awsglobalaccelerator.com`
NS	`ns2.mysecurecloudhost.com` ⚠️ Not in zone NS records
		A	75.2.118.134^{🇺🇸 Amazon75.2.112.0/20}
			PTR	`abc65dd9a44b5332f.awsglobalaccelerator.com`
NS	`ns2.us17.tmd.cloud` ⚠️ Not in parent delegation
		A	13.248.158.180^{🇺🇸 Amazon13.248.144.0/20}
			PTR	`a79764cc55c0ac9c0.awsglobalaccelerator.com`
NS	`ns3.mysecurecloudhost.com` ⚠️ Not in zone NS records
		A	76.223.26.245^{🇺🇸 Amazon76.223.16.0/20}
			PTR	`a79764cc55c0ac9c0.awsglobalaccelerator.com`
NS	`ns4.mysecurecloudhost.com` ⚠️ Not in zone NS records
		A	99.83.147.209^{🇺🇸 Amazon99.83.144.0/20}
			PTR	`abc65dd9a44b5332f.awsglobalaccelerator.com`
MX	`beacondigitals.com` ⭐
		A	192.250.227.243^{🇬🇧 WHG-DAL192.250.227.0/24}
			PTR	`s12772.usc1.stableserver.net`
TXT	`v=spf1 +a +mx +ip4:192.250.227.243 include:spf.mysecurecloudhost.com ~all`
SOA	`ns1.us17.tmd.cloud`servers@mysecurecloudhost.com 2026-05-14 #0

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

MX for

beacondigitals.com

Same first word

beacondigitals.com

DNS History

13 records (8 active, 5 former)

●NSns1.mysecurecloudhost.com2026-03-30 → 2026-05-14 · 3 obs

○ 2019-01-19 18:36:02
● 2026-03-30 06:31:10
● 2026-05-14 13:18:58

○NSns1.netfirms.com2017-02-07 → 2019-01-19 · 4 obs

● 2017-02-07 20:56:26
● 2019-01-19 18:36:02
○ 2026-03-30 06:31:10
○ 2026-05-14 13:18:58

●NSns1.us17.tmd.cloud2026-03-30 → 2026-05-14 · 3 obs

○ 2019-01-19 18:36:02
● 2026-03-30 06:31:10
● 2026-05-14 13:18:58

●NSns2.mysecurecloudhost.com2026-03-30 → 2026-05-14 · 3 obs

○ 2019-01-19 18:36:02
● 2026-03-30 06:31:10
● 2026-05-14 13:18:58

○NSns2.netfirms.com2017-02-07 → 2019-01-19 · 4 obs

● 2017-02-07 20:56:26
● 2019-01-19 18:36:02
○ 2026-03-30 06:31:10
○ 2026-05-14 13:18:58

●NSns2.us17.tmd.cloud2026-03-30 → 2026-05-14 · 3 obs

○ 2019-01-19 18:36:02
● 2026-03-30 06:31:10
● 2026-05-14 13:18:58

●NSns3.mysecurecloudhost.com2026-03-30 → 2026-05-14 · 3 obs

○ 2019-01-19 18:36:02
● 2026-03-30 06:31:10
● 2026-05-14 13:18:58

●NSns4.mysecurecloudhost.com2026-03-30 → 2026-05-14 · 3 obs

○ 2019-01-19 18:36:02
● 2026-03-30 06:31:10
● 2026-05-14 13:18:58

●MXbeacondigitals.com2026-03-30 → 2026-05-14 · 3 obs

○ 2019-01-19 18:36:02
● 2026-03-30 06:31:10
● 2026-05-14 13:18:58

○MXmx.beacondigitals.com2017-02-07 → 2019-01-19 · 4 obs

● 2017-02-07 20:56:26
● 2019-01-19 18:36:02
○ 2026-03-30 06:31:10
○ 2026-05-14 13:18:58

●A192.250.227.2432026-03-30 → 2026-05-14 · 3 obs

○ 2019-01-19 18:36:02
● 2026-03-30 06:31:10
● 2026-05-14 13:18:58

○A66.96.149.12017-02-07 → 2019-01-19 · 5 obs

○ 2016-03-23 00:31:56
● 2017-02-07 20:56:26
● 2019-01-19 18:36:02
○ 2026-03-30 06:31:10
○ 2026-05-14 13:18:58

○A74.220.199.142015-08-20 → 2016-03-23 · 4 obs

● 2015-08-20 08:30:16
● 2016-03-23 00:31:56
○ 2017-02-07 20:56:26
○ 2026-05-14 13:18:58

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
beacondigitals.com	ns1.mysecurecloudhost.com, ns2.mysecurecloudhost.com, ns3.mysecurecloudhost.com, ns4.mysecurecloudhost.com	4 records

✅ Authoritative Response

Server:75.2.118.134

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for beacondigitals.com (unsigned zone)

⏱️ Timing

Total: 347ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`192.250.227.243`
NS	2	`ns1.us17.tmd.cloud, ns2.us17.tmd.cloud`
MX	1	`beacondigitals.com (pri: 0)`
TXT	1	`v=spf1 +a +mx +ip4:192.250.227.243 inclu`
SOA	1	`ns1.us17.tmd.cloud servers.mysecurecloud`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns1.mysecurecloudhost.com, ns2.mysecurecloudhost.com, ns3.mysecurecloudhost.com...)

Analysis

Mail Server Role

beacondigitals.com serves as the mail server for beacondigitals.com.

IP Addresses

beacondigitals.com points to IP number 192.250.227.243.

For instance, other host names shopmelt.com, mfss.org, ihatebadmovies.com, ricksworkshop.org and redappledxb.com share IP numbers with beacondigitals.com.

Name Servers

beacondigitals.com is delegated to six name servers: ns1.mysecurecloudhost.com, ns2.mysecurecloudhost.com, ns3.mysecurecloudhost.com, ns4.mysecurecloudhost.com, ns1.us17.tmd.cloud and ns2.us17.tmd.cloud.

beacondigitals.com shares name servers with other domains at least partially, for example quantum.edu.np, brucke.es, lrcricket.com, thirteeneighty.co.uk and routinescape.com.

These name servers are commonly used together with ns1.s410.tmd.cloud, ns2.s410.tmd.cloud, ns1.s510.tmd.cloud and ns2.s510.tmd.cloud.

Host names with a single IP number: ns1.mysecurecloudhost.com points to: 13.248.158.180; ns2.mysecurecloudhost.com points to: 75.2.118.134; ns3.mysecurecloudhost.com points to: 76.223.26.245; ns4.mysecurecloudhost.com points to: 99.83.147.209; ns1.us17.tmd.cloud points to: 13.248.158.180; ns2.us17.tmd.cloud points to: 13.248.158.180. Hosts that point to 13.248.158.180: ns1.mysecurecloudhost.com, ns1.us17.tmd.cloud and ns2.us17.tmd.cloud.

Mail Servers

beacondigitals.com is handled by a single mail server, beacondigitals.com.

beacondigitals.com points to a single IP: 192.250.227.243.

beacondigitals.com - robtex.com