datingtorelating.com - dns.ninja

`datingtorelating.com`

DNSSEC	⚠️ Not signed
A	2600:1f18:14cf:6203:7116:ee00:bf53:f124^{🇺🇸 Amazon2600:1f18::/35 AMAZON EC2 IAD prefix} ✓ In HTTPS hints
A	3.208.18.201^{🇺🇸 Amazon3.208.0.0/12 EC2 IAD prefix} ✓ In HTTPS hints
NS	`dns2.ezot.com` ⭐ ⚠️ Not in parent delegation
		A	44.229.104.104^{🇺🇸 Amazon44.224.0.0/11 EC2 PDX prefix}
			PTR	`ec2-44-229-104-104.us-west-2.compute.amazonaws.com`
NS	`dns.bizsiteservice.com` ⚠️ Not in zone NS records
		A	2600:1f16:e7a:5000:145a:29bb:458a:27bb^{🇺🇸 Amazon2600:1f16:c00::/38 AMAZON AWS}
		A	3.19.51.56^{🇺🇸 Amazon3.16.0.0/14 EC2 CMH prefix}
			PTR	`ec2-3-19-51-56.us-east-2.compute.amazonaws.com`
NS	`dns.ezot.com` ⚠️ Not in parent delegation
		A	3.19.51.56^{🇺🇸 Amazon3.16.0.0/14 EC2 CMH prefix}
			PTR	`ec2-3-19-51-56.us-east-2.compute.amazonaws.com`
NS	`dns2.bizsiteservice.com` ⚠️ Not in zone NS records
		A	2600:1f13:b23:5f00:90a7:bd94:1ad1:e404^{🇺🇸 Amazon2600:1f13::/36 EC2 PDX prefix}
		A	44.229.104.104^{🇺🇸 Amazon44.224.0.0/11 EC2 PDX prefix}
			PTR	`ec2-44-229-104-104.us-west-2.compute.amazonaws.com`
MX	`x34.b5z.net` ⭐
		A	69.7.174.58^{🇺🇸 DATABANK69.7.160.0/19 Databank HOU}
			PTR	`w58.ezot.com`
MX	`x50.b5z.net`⁽²⁰⁾
		A	18.191.44.123^{🇺🇸 Amazon18.191.0.0/16 EC2 CMH prefix}
			PTR	`ec2-18-191-44-123.us-east-2.compute.amazonaws.com`
TXT	`v=spf1 mx ip4:69.7.164.160/24 ip4:69.7.169.70/24 ip4:69.7.180.116/24 ip4:69.7...`
HTTPS	HTTP/2, HTTP/3 ✓ hints match
		IPv4 hints	3.208.18.201
		IPv6 hints	2600:1f18:14cf:6203:7116:ee00:bf53:f124
SOA	`dns.ezot.com`dns@ezot.com serial=20260511

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

WOT: UNKNOWN (50/100)

Same first word

datingtorelating.net

datingtorelating.info

datingtorelating.com

DNS History

12 records (8 active, 4 former)

●NSdns.bizsiteservice.com2015-08-22 → 2026-07-23 · 2 obs

● 2015-08-22 02:19:42
● 2026-07-23 22:41:06

●NSdns.ezot.com2026-04-14 → 2026-07-23 · 3 obs

○ 2015-08-22 02:19:42
● 2026-04-14 20:03:32
● 2026-07-23 22:41:06

●NSdns2.bizsiteservice.com2015-08-22 → 2026-07-23 · 2 obs

● 2015-08-22 02:19:42
● 2026-07-23 22:41:06

●NSdns2.ezot.com2026-04-14 → 2026-07-23 · 3 obs

○ 2015-08-22 02:19:42
● 2026-04-14 20:03:32
● 2026-07-23 22:41:06

○MXmail34.ezot.com2015-08-22 → 2017-01-30 · 4 obs

● 2015-08-22 02:19:42
● 2017-01-30 16:09:56
○ 2026-02-16 22:00:30
○ 2026-07-23 22:41:06

●MXx34.b5z.net2026-04-14 → 2026-07-23 · 3 obs

○ 2026-02-20 06:25:14
● 2026-04-14 20:03:32
● 2026-07-23 22:41:06

○MXx34.bizsiteservice.com2026-02-16 → 2026-02-20 · 5 obs

○ 2017-01-30 16:09:56
● 2026-02-16 22:00:30
● 2026-02-20 06:25:14
○ 2026-04-14 20:03:32
○ 2026-07-23 22:41:06

●MXx50.b5z.net2026-04-14 → 2026-07-23 · 3 obs

○ 2026-02-20 06:25:14
● 2026-04-14 20:03:32
● 2026-07-23 22:41:06

○MXx50.bizsiteservice.com2015-08-22 → 2026-02-20 · 4 obs

● 2015-08-22 02:19:42
● 2026-02-20 06:25:14
○ 2026-04-14 20:03:32
○ 2026-07-23 22:41:06

●A2600:1f18:14cf:6203:7116:ee00:bf53:f1242026-02-16 → 2026-07-23 · 3 obs

○ 2017-01-30 16:09:56
● 2026-02-16 22:00:30
● 2026-07-23 22:41:06

●A3.208.18.2012026-02-16 → 2026-07-23 · 3 obs

○ 2017-01-30 16:09:56
● 2026-02-16 22:00:30
● 2026-07-23 22:41:06

○A69.7.174.332015-08-22 → 2017-01-30 · 4 obs

● 2015-08-22 02:19:42
● 2017-01-30 16:09:56
○ 2026-02-16 22:00:30
○ 2026-07-23 22:41:06

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
datingtorelating.com	dns.bizsiteservice.com, dns2.bizsiteservice.com	2 records

✅ Authoritative Response

Server:44.229.104.104

NS records: dns.bizsiteservice.com, dns2.bizsiteservice.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for datingtorelating.com (unsigned zone)

⏱️ Timing

Total: 356ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`3.208.18.201`
AAAA	1	`2600:1f18:14cf:6203:7116:ee00:bf53:f124`
NS	2	`dns.ezot.com, dns2.ezot.com`
MX	2	`x34.b5z.net (pri: 5), x50.b5z.net (pri: 20)`
TXT	1	`v=spf1 mx ip4:69.7.164.160/24 ip4:69.7.1`
HTTPS	1	`{"priority":1,"target":".","alpn":["h2",`
SOA	1	`dns.ezot.com dns.ezot.com`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (dns.bizsiteservice.com, dns2.bizsiteservice.com)

Analysis

IP Addresses

datingtorelating.com points to the IP addresses 3.208.18.201 and 2600:1f18:14cf:6203:7116:ee00:bf53:f124

makeitloudsites.com, sitehatcher.com, ezwebsites.biz plus two other host names have IP numbers in common with datingtorelating.com.

Name Servers

Four name servers handle the delegation for datingtorelating.com: dns2.bizsiteservice.com, dns.bizsiteservice.com, dns2.ezot.com and dns.ezot.com.

The name servers of datingtorelating.com overlap at least partially with those of other domains — among them commercialcleaningwestmonroe.com, margieandpaul.com, taytos.com and two more.

Host names pointing to two IP addresses:

dns2.bizsiteservice.com resolves to 44.229.104.104 and 2600:1f13:b23:5f00:90a7:bd94:1ad1:e404.

dns.bizsiteservice.com resolves to 3.19.51.56 and 2600:1f16:e7a:5000:145a:29bb:458a:27bb.

Host names resolving to a single IP address:

dns2.ezot.com resolves to 44.229.104.104.

dns.ezot.com resolves to 3.19.51.56.

The host names dns2.bizsiteservice.com and dns2.ezot.com both resolve to 44.229.104.104 IP addresses.

The host names dns.bizsiteservice.com and dns.ezot.com both resolve to 3.19.51.56 IP addresses.

Mail Servers

datingtorelating.com uses two mail servers, x34.b5z.net and x50.b5z.net.

The mail server setup of datingtorelating.com matches that of other domains such as makeitloudsites.com, burnsidegarage.co.uk, praynky.com and two others.

Both x34.b5z.net and x50.b5z.net have a single IP address each — x34.b5z.net resolves to 69.7.174.58 while x50.b5z.net resolves to 18.191.44.123.