`beautifulrussianbride.com`

DNSSEC	⚠️ Not signed
A	3.216.173.128^{🇺🇸 Amazon3.208.0.0/12 EC2 IAD prefix}
		PTR	`ec2-3-216-173-128.compute-1.amazonaws.com`
NS	`dns1.agaceri.net` ⭐
		A	3.216.173.128^{🇺🇸 Amazon3.208.0.0/12 EC2 IAD prefix}
			PTR	`ec2-3-216-173-128.compute-1.amazonaws.com`
NS	`dns2.agaceri.net`
		A	104.250.116.22^{🇺🇸 AS40676104.250.116.0/24 265 Franklin Street, Suite 1702 Boston MA 02110 United States}
SOA	`dns1.agaceri.net`whois@beautifulrussianbride.com 2025-05-16 #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=1776141267

Subdomains

nullmx.beautifulrussianbride.com

Same first word

beautifulrussianbride.com

DNS History

12 records (3 active, 9 former)

●NSdns1.agaceri.net2026-04-14 → 2026-04-14 · 2 obs

○ 2020-01-29 05:26:22
● 2026-04-14 04:35:48

●NSdns2.agaceri.net2026-04-14 → 2026-04-14 · 2 obs

○ 2020-01-29 05:26:22
● 2026-04-14 04:35:48

○NSns1.hitfarm.com2008-03-15 → 2008-03-15 · 3 obs

● 2008-03-15 23:38:46
○ 2015-07-16 04:32:14
○ 2026-04-14 04:35:48

○NSns2.hitfarm.com2008-03-15 → 2008-03-15 · 3 obs

● 2008-03-15 23:38:46
○ 2015-07-16 04:32:14
○ 2026-04-14 04:35:48

○NSns3.hitfarm.com2008-03-15 → 2008-03-15 · 3 obs

● 2008-03-15 23:38:46
○ 2015-07-16 04:32:14
○ 2026-04-14 04:35:48

○NSns75.domaincontrol.com2015-07-16 → 2020-01-29 · 4 obs

○ 2008-03-15 23:38:46
● 2015-07-16 04:32:14
● 2020-01-29 05:26:22
○ 2026-04-14 04:35:48

○NSns76.domaincontrol.com2015-07-16 → 2020-01-29 · 4 obs

○ 2008-03-15 23:38:46
● 2015-07-16 04:32:14
● 2020-01-29 05:26:22
○ 2026-04-14 04:35:48

○MXmail.beautifulrussianbride.com2015-07-16 → 2020-01-29 · 4 obs

○ 2008-03-15 23:38:46
● 2015-07-16 04:32:14
● 2020-01-29 05:26:22
○ 2026-04-14 04:35:48

○MXnullmx.beautifulrussianbride.com2008-03-15 → 2008-03-15 · 3 obs

● 2008-03-15 23:38:46
○ 2015-07-16 04:32:14
○ 2026-04-14 04:35:48

○A173.255.195.642015-07-16 → 2020-01-29 · 4 obs

○ 2008-03-15 23:38:46
● 2015-07-16 04:32:14
● 2020-01-29 05:26:22
○ 2026-04-14 04:35:48

○A217.68.70.692008-03-15 → 2008-03-15 · 3 obs

● 2008-03-15 23:38:46
○ 2015-07-16 04:32:14
○ 2026-04-14 04:35:48

●A3.216.173.1282026-04-14 → 2026-04-14 · 2 obs

○ 2020-01-29 05:26:22
● 2026-04-14 04:35:48

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net...	-
beautifulrussianbride.com	dns1.agaceri.net, dns2.agaceri.net	-

✅ Authoritative Response

Server:3.216.173.128

NS records: dns1.agaceri.net, dns2.agaceri.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for beautifulrussianbride.com (unsigned zone)

⏱️ Timing

Total: 3403ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`3.216.173.128`
NS	2	`dns2.agaceri.net, dns1.agaceri.net`
SOA	1	`dns1.agaceri.net whois.beautifulrussianb`

Analysis

Hierarchy

beautifulrussianbride.com is parent of nullmx.beautifulrussianbride.com.

IP Addresses

beautifulrussianbride.com points to a single IP: 3.216.173.128.

Other host names, for instance ec2-3-216-173-128.compute-1.amazonaws.com, dns1.agaceri.net, vidok.org, nmlodging.org and agfanet.com share IP numbers with beautifulrussianbride.com.

Name Servers

beautifulrussianbride.com's delegation is to two name servers dns1.agaceri.net and dns2.agaceri.net.

beautifulrussianbride.com uses the same name server setup as other domains, including nmlodging.org, agfanet.com, cau-llc.com and vidok.org.

Host names with a single IP:

dns1.agaceri.net resolves to 3.216.173.128.

dns2.agaceri.net resolves to 104.250.116.22.

beautifulrussianbride.com - robtex.com