`relationalmissions.com`

DNSSEC	⚠️ Not signed
A	148.105.251.19^{🇺🇸 THEROCKETSCIENCEGROUP148.105.251.0/24}
NS	`ns1.systemdns.com` ⭐
		A	2604:4000:0:d:216:40:47:90^{🇨🇦 TUCOWS2604:4000::/48 -BRA-IPV6-BLK1.1/NET-2604:4000}
			PTR	`ns1.systemdns.com`
		A	216.40.47.90^{🇨🇦 TUCOWS216.40.47.0/24 -BRA-BLK1.4/NET-216-40-47-0}
			PTR	`ns1.systemdns.com`
NS	`ns2.systemdns.com`
		A	2604:4000:2800:d:64:99:148:16^{🇨🇦 TUCOWS-32604:4000:2800::/37 Tucows.com Co.}
			PTR	`ns2.systemdns.com`
		A	64.98.148.16^{🇨🇦 TUCOWS-364.98.144.0/20 Tucows.com Co.}
			PTR	`ns2.systemdns.com`
NS	`ns3.systemdns.com`
		A	2604:4000:0:d:64:99:96:36^{🇨🇦 TUCOWS2604:4000::/48 -BRA-IPV6-BLK1.1/NET-2604:4000}
			PTR	`ns3.systemdns.com`
		A	64.99.96.36^{🇨🇦 TUCOWS64.99.96.0/24 -BRA-BLK2.7.2}
			PTR	`ns3.systemdns.com`
MX	`mx.relationalmissions.com.cust.b.hostedemail.com` ⭐
		A	64.98.38.4^{🇨🇦 TUCOWS-364.98.38.0/24 IPv4 Allow}
			PTR	`mx.b.hostedemail.com`
SOA	`ns1.systemdns.com`hostmaster@systemdns.com serial=1709849071

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

Same first word

relationalmissions.com

DNS History

5 records (5 active, 0 former)

●NSns1.systemdns.com2026-04-11 → 2026-04-13 · 2 obs

● 2026-04-11 04:16:52
● 2026-04-13 20:10:04

●NSns2.systemdns.com2026-04-11 → 2026-04-13 · 2 obs

● 2026-04-11 04:16:52
● 2026-04-13 20:10:04

●NSns3.systemdns.com2026-04-11 → 2026-04-13 · 2 obs

● 2026-04-11 04:16:52
● 2026-04-13 20:10:04

●MXmx.relationalmissions.com.cust.b.hostedemail.com2026-04-11 → 2026-04-13 · 2 obs

● 2026-04-11 04:16:52
● 2026-04-13 20:10:04

●A148.105.251.192026-04-11 → 2026-04-13 · 2 obs

● 2026-04-11 04:16:52
● 2026-04-13 20:10:04

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	i.gtld-servers.net, g.gtld-servers.net, a.gtld-servers.net, m.gtld-servers.net...	-
relationalmissions.com	ns1.systemdns.com, ns2.systemdns.com, ns3.systemdns.com	6 records

✅ Authoritative Response

Server:64.98.148.16

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for relationalmissions.com (unsigned zone)

⏱️ Timing

Total: 221ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`148.105.251.19`
NS	3	`ns1.systemdns.com, ns2.systemdns.com...`
MX	1	`mx.relationalmissions.com.cust.b.hostede`
SOA	1	`ns1.systemdns.com hostmaster.systemdns.c`

📌 Glue Records Collected

Total: 6

Out-of-bailiwick: 6 (ns1.systemdns.com, ns1.systemdns.com, ns2.systemdns.com...)

Analysis

IP Addresses

relationalmissions.com maps to IP address 148.105.251.19.

Other host names, for instance shaunaford.com, broadex-tech.co.uk, artur-deinfinanzcoach.de, congressionalcatholicstaff.com and burgundyasset.com share IP numbers with relationalmissions.com.

Name Servers

relationalmissions.com is delegated to name servers ns1.systemdns.com, ns2.systemdns.com and ns3.systemdns.com.

relationalmissions.com at least partially shares name servers with other domains such as nearestexit.net, share(0x787878).com, bustrade.net, makeyourlogos.com and elbaelettromedicali.it.

Host names with two IP numbers:

ns1.systemdns.com points to 2604:4000:0:d:216:40:47:90 and 216.40.47.90.

ns2.systemdns.com points to 2604:4000:2800:d:64:99:148:16 and 64.98.148.16.

ns3.systemdns.com points to 2604:4000:0:d:64:99:96:36 and 64.99.96.36.

Mail Servers

relationalmissions.com is handled by a single mail server, mx.relationalmissions.com.cust.b.hostedemail.com.

mx.relationalmissions.com.cust.b.hostedemail.com points to one IP number: 64.98.38.4.

relationalmissions.com - robtex.com