`bridalflowerdivas.com`

DNSSEC	⚠️ Not signed
A	38.154.81.138^{🇺🇸 SERVER-MANIA38.154.80.0/22}
NS	`ns1.md-dym-iqsv.com` ⭐
		A	18.176.103.149^{🇯🇵 Amazon18.176.0.0/15 EC2 NRT prefix}
			PTR	`ec2-18-176-103-149.ap-northeast-1.compute.amazonaws.com`
NS	`ns2.md-dym-iqsv.com`
		A	35.72.51.209^{🇯🇵 Amazon35.72.0.0/13 EC2 NRT prefix}
			PTR	`ec2-35-72-51-209.ap-northeast-1.compute.amazonaws.com`
MX	`bridalflowerdivas.com` ⭐
		A	38.154.81.138^{🇺🇸 SERVER-MANIA38.154.80.0/22}
SOA	`ns1.md-dym-iqsv.com`root@dymweb1.md-dym-iqsv.com 2025-10-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=1774801612

MX for

bridalflowerdivas.com

Same first word

bridalflowerdivas.com

DNS History

20 records (4 active, 16 former)

○NSeva.ns.cloudflare.com2015-07-10 → 2015-11-14 · 4 obs

● 2015-07-10 22:21:34
● 2015-11-14 21:18:32
○ 2016-02-12 21:29:22
○ 2026-03-29 16:37:14

○NSns09.domaincontrol.com2016-02-12 → 2016-02-12 · 4 obs

○ 2015-11-14 21:18:32
● 2016-02-12 21:29:22
○ 2016-06-25 10:55:46
○ 2026-03-29 16:37:14

○NSns1.7cloudcomputing.com2016-06-25 → 2017-03-20 · 5 obs

○ 2016-02-12 21:29:22
● 2016-06-25 10:55:46
● 2017-03-20 06:57:34
○ 2026-03-27 18:31:24
○ 2026-03-29 16:37:14

●NSns1.md-dym-iqsv.com2026-03-27 → 2026-03-29 · 3 obs

○ 2017-03-20 06:57:34
● 2026-03-27 18:31:24
● 2026-03-29 16:37:14

○NSns10.domaincontrol.com2016-02-12 → 2016-02-12 · 4 obs

○ 2015-11-14 21:18:32
● 2016-02-12 21:29:22
○ 2016-06-25 10:55:46
○ 2026-03-29 16:37:14

○NSns2.7cloudcomputing.com2016-06-25 → 2017-03-20 · 5 obs

○ 2016-02-12 21:29:22
● 2016-06-25 10:55:46
● 2017-03-20 06:57:34
○ 2026-03-27 18:31:24
○ 2026-03-29 16:37:14

●NSns2.md-dym-iqsv.com2026-03-27 → 2026-03-29 · 3 obs

○ 2017-03-20 06:57:34
● 2026-03-27 18:31:24
● 2026-03-29 16:37:14

○NSsam.ns.cloudflare.com2015-07-10 → 2015-11-14 · 4 obs

● 2015-07-10 22:21:34
● 2015-11-14 21:18:32
○ 2016-02-12 21:29:22
○ 2026-03-29 16:37:14

○MXalt1.aspmx.l.google.com2015-07-10 → 2015-11-14 · 4 obs

● 2015-07-10 22:21:34
● 2015-11-14 21:18:32
○ 2016-02-12 21:29:22
○ 2026-03-29 16:37:14

○MXalt2.aspmx.l.google.com2015-07-10 → 2015-11-14 · 4 obs

● 2015-07-10 22:21:34
● 2015-11-14 21:18:32
○ 2016-02-12 21:29:22
○ 2026-03-29 16:37:14

○MXaspmx.l.google.com2015-07-10 → 2015-11-14 · 4 obs

● 2015-07-10 22:21:34
● 2015-11-14 21:18:32
○ 2016-02-12 21:29:22
○ 2026-03-29 16:37:14

○MXaspmx2.googlemail.com2015-07-10 → 2015-11-14 · 4 obs

● 2015-07-10 22:21:34
● 2015-11-14 21:18:32
○ 2016-02-12 21:29:22
○ 2026-03-29 16:37:14

○MXaspmx3.googlemail.com2015-07-10 → 2015-11-14 · 4 obs

● 2015-07-10 22:21:34
● 2015-11-14 21:18:32
○ 2016-02-12 21:29:22
○ 2026-03-29 16:37:14

●MXbridalflowerdivas.com2016-06-25 → 2026-03-29 · 3 obs

○ 2016-02-12 21:29:22
● 2016-06-25 10:55:46
● 2026-03-29 16:37:14

○MXmailstore1.secureserver.net2016-02-12 → 2016-02-12 · 4 obs

○ 2015-11-14 21:18:32
● 2016-02-12 21:29:22
○ 2016-06-25 10:55:46
○ 2026-03-29 16:37:14

○MXsmtp.secureserver.net2016-02-12 → 2016-02-12 · 4 obs

○ 2015-11-14 21:18:32
● 2016-02-12 21:29:22
○ 2016-06-25 10:55:46
○ 2026-03-29 16:37:14

○A129.121.22.682016-06-25 → 2017-03-20 · 5 obs

○ 2016-02-12 21:29:22
● 2016-06-25 10:55:46
● 2017-03-20 06:57:34
○ 2026-03-27 18:31:24
○ 2026-03-29 16:37:14

○A184.168.221.582016-02-12 → 2016-02-12 · 4 obs

○ 2015-11-14 21:18:32
● 2016-02-12 21:29:22
○ 2016-06-25 10:55:46
○ 2026-03-29 16:37:14

●A38.154.81.1382026-03-27 → 2026-03-29 · 3 obs

○ 2017-03-20 06:57:34
● 2026-03-27 18:31:24
● 2026-03-29 16:37:14

○A50.28.24.962015-07-10 → 2015-11-14 · 4 obs

● 2015-07-10 22:21:34
● 2015-11-14 21:18:32
○ 2016-02-12 21:29:22
○ 2026-03-29 16:37:14

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	e.gtld-servers.net, h.gtld-servers.net, m.gtld-servers.net, l.gtld-servers.net...	-
bridalflowerdivas.com	ns1.md-dym-iqsv.com, ns2.md-dym-iqsv.com	2 records

✅ Authoritative Response

Server:18.176.103.149

NS records: ns1.md-dym-iqsv.com, ns2.md-dym-iqsv.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for bridalflowerdivas.com (unsigned zone)

⏱️ Timing

Total: 393ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`38.154.81.138`
NS	2	`ns2.md-dym-iqsv.com, ns1.md-dym-iqsv.com`
MX	1	`bridalflowerdivas.com (pri: 0)`
SOA	1	`ns1.md-dym-iqsv.com root.dymweb1.md-dym-`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.md-dym-iqsv.com, ns2.md-dym-iqsv.com)

Analysis

Mail Server Role

The mail server for bridalflowerdivas.com is bridalflowerdivas.com.

IP Addresses

bridalflowerdivas.com maps to IP address 38.154.81.138.

Other host names, for example guthriegenealogy.com, otohi.com and toilet-paper-stand.com share the same IP as bridalflowerdivas.com.

Name Servers

Two name servers ns1.md-dym-iqsv.com and ns2.md-dym-iqsv.com are delegated to bridalflowerdivas.com.

bridalflowerdivas.com uses the same name server configuration as other domains, such as intervaltogo.com, ural74.com, mediterraneanco.com, kingstaa.net and business-growth-strategies.com.

Host names with a single IP address:

ns1.md-dym-iqsv.com points to 18.176.103.149

ns2.md-dym-iqsv.com points to 35.72.51.209

Mail Servers

One mail server serves bridalflowerdivas.com.

bridalflowerdivas.com points to one IP number: 38.154.81.138.

bridalflowerdivas.com - robtex.com