`weddingtobe.com`

DNSSEC	⚠️ Not signed
A	2600:1f18:4ae:c605:dd5d:b838:5816:d7fb^{🇺🇸 Amazon2600:1f18::/35 AMAZON EC2 IAD prefix}
A	2600:1f18:4ae:c606:78d4:4260:db4e:aeee^{🇺🇸 Amazon2600:1f18::/35 AMAZON EC2 IAD prefix}
A	13.223.25.84^{🇺🇸 Amazon13.216.0.0/13 EC2 IAD prefix}
A	54.243.117.197^{🇺🇸 Amazon54.242.0.0/15 EC2 IAD prefix}
NS	`ns1.namebrightdns.com` ⭐
		A	2600:1f18:683a:ae1a:aa86:dc69:2f3:5dbe^{🇺🇸 Amazon2600:1f18:6000::/35 AMAZON EC2 IAD prefix}
		A	2600:1f18:683a:ae1b:3376:e04f:851f:406c^{🇺🇸 Amazon2600:1f18:6000::/35 AMAZON EC2 IAD prefix}
		A	2600:1f18:683a:ae1b:a510:c365:d06a:e73a^{🇺🇸 Amazon2600:1f18:6000::/35 AMAZON EC2 IAD prefix}
		A	52.91.47.137^{🇺🇸 Amazon52.90.0.0/15 EC2 IAD prefix}
			PTR	`ec2-52-91-47-137.compute-1.amazonaws.com`
		A	54.92.199.119^{🇺🇸 Amazon54.92.128.0/17 EC2 IAD prefix}
			PTR	`ec2-54-92-199-119.compute-1.amazonaws.com`
		A	98.83.163.23^{🇺🇸 Amazon98.80.0.0/13 EC2 IAD Prefix}
			PTR	`ec2-98-83-163-23.compute-1.amazonaws.com`
NS	`nsg1.namebrightdns.com`
		A	2600:1f18:683a:ae1a:5c5e:bc55:1478:cf93^{🇺🇸 Amazon2600:1f18:6000::/35 AMAZON EC2 IAD prefix}
		A	2600:1f18:683a:ae1a:e5a9:8ee2:a408:496a^{🇺🇸 Amazon2600:1f18:6000::/35 AMAZON EC2 IAD prefix}
		A	2600:1f18:683a:ae1a:e842:8110:107c:b494^{🇺🇸 Amazon2600:1f18:6000::/35 AMAZON EC2 IAD prefix}
		A	2600:1f18:683a:ae1b:a136:1971:9598:5d4a^{🇺🇸 Amazon2600:1f18:6000::/35 AMAZON EC2 IAD prefix}
		A	13.221.125.168^{🇺🇸 Amazon13.216.0.0/13 EC2 IAD prefix}
			PTR	`ec2-13-221-125-168.compute-1.amazonaws.com`
		A	23.22.234.151^{🇺🇸 Amazon23.22.0.0/15 EC2 IAD prefix}
			PTR	`ec2-23-22-234-151.compute-1.amazonaws.com`
		A	44.220.149.224^{🇺🇸 Amazon44.192.0.0/11 EC2 IAD prefix}
			PTR	`ec2-44-220-149-224.compute-1.amazonaws.com`
		A	54.90.222.89^{🇺🇸 Amazon54.90.0.0/15 EC2 IAD prefix}
			PTR	`ec2-54-90-222-89.compute-1.amazonaws.com`
NS	`nsg2.namebrightdns.com`
		A	2600:1f18:683a:ae1a:e1f7:fcf3:dce8:5758^{🇺🇸 Amazon2600:1f18:6000::/35 AMAZON EC2 IAD prefix}
		A	2600:1f18:683a:ae1b:130f:6e59:4e36:8c1e^{🇺🇸 Amazon2600:1f18:6000::/35 AMAZON EC2 IAD prefix}
		A	2600:1f18:683a:ae1b:9806:d504:f0e4:26c^{🇺🇸 Amazon2600:1f18:6000::/35 AMAZON EC2 IAD prefix}
		A	2600:1f18:683a:ae1b:eda8:cb11:b8f:c1fe^{🇺🇸 Amazon2600:1f18:6000::/35 AMAZON EC2 IAD prefix}
		A	3.82.54.251^{🇺🇸 Amazon3.80.0.0/12 EC2 IAD prefix}
			PTR	`ec2-3-82-54-251.compute-1.amazonaws.com`
		A	3.85.217.230^{🇺🇸 Amazon3.80.0.0/12 EC2 IAD prefix}
			PTR	`ec2-3-85-217-230.compute-1.amazonaws.com`
		A	3.89.204.207^{🇺🇸 Amazon3.80.0.0/12 EC2 IAD prefix}
			PTR	`ec2-3-89-204-207.compute-1.amazonaws.com`
		A	98.93.89.251^{🇺🇸 Amazon98.88.0.0/13 EC2 IAD prefix}
			PTR	`ec2-98-93-89-251.compute-1.amazonaws.com`
TXT	`v=spf1 -all`
TXT	`afternic-verification-G9G3tM8T8EwEizzPzjGJWF`
SOA	`ns1.namebrightdns.com`dns@namebright.com 2026-03-24 #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=1774391212

Same first word

weddingtobe.com

DNS History

16 records (7 active, 9 former)

○NSdns1.name-services.com2016-03-07 → 2017-02-12 · 4 obs

● 2016-03-07 00:56:42
● 2017-02-12 09:54:20
○ 2018-07-31 20:43:42
○ 2026-03-24 22:35:50

○NSdns2.name-services.com2016-03-07 → 2017-02-12 · 4 obs

● 2016-03-07 00:56:42
● 2017-02-12 09:54:20
○ 2018-07-31 20:43:42
○ 2026-03-24 22:35:50

○NSdns3.name-services.com2016-03-07 → 2017-02-12 · 4 obs

● 2016-03-07 00:56:42
● 2017-02-12 09:54:20
○ 2018-07-31 20:43:42
○ 2026-03-24 22:35:50

○NSdns4.name-services.com2016-03-07 → 2017-02-12 · 4 obs

● 2016-03-07 00:56:42
● 2017-02-12 09:54:20
○ 2018-07-31 20:43:42
○ 2026-03-24 22:35:50

○NSdns5.name-services.com2016-03-07 → 2017-02-12 · 4 obs

● 2016-03-07 00:56:42
● 2017-02-12 09:54:20
○ 2018-07-31 20:43:42
○ 2026-03-24 22:35:50

●NSns1.namebrightdns.com2018-07-31 → 2026-03-24 · 3 obs

○ 2017-02-12 09:54:20
● 2018-07-31 20:43:42
● 2026-03-24 22:35:50

○NSns2.namebrightdns.com2018-07-31 → 2018-07-31 · 3 obs

○ 2017-02-12 09:54:20
● 2018-07-31 20:43:42
○ 2026-03-24 22:35:50

●NSnsg1.namebrightdns.com2026-03-24 → 2026-03-24 · 2 obs

○ 2018-07-31 20:43:42
● 2026-03-24 22:35:50

●NSnsg2.namebrightdns.com2026-03-24 → 2026-03-24 · 2 obs

○ 2018-07-31 20:43:42
● 2026-03-24 22:35:50

●A13.223.25.842026-03-24 → 2026-03-24 · 2 obs

○ 2018-07-31 20:43:42
● 2026-03-24 22:35:50

●A2600:1f18:4ae:c605:dd5d:b838:5816:d7fb2026-03-24 → 2026-03-24 · 2 obs

○ 2018-07-31 20:43:42
● 2026-03-24 22:35:50

●A2600:1f18:4ae:c606:78d4:4260:db4e:aeee2026-03-24 → 2026-03-24 · 2 obs

○ 2018-07-31 20:43:42
● 2026-03-24 22:35:50

●A54.243.117.1972026-03-24 → 2026-03-24 · 2 obs

○ 2018-07-31 20:43:42
● 2026-03-24 22:35:50

○A8.5.1.432017-02-12 → 2017-02-12 · 4 obs

○ 2016-06-25 19:38:52
● 2017-02-12 09:54:20
○ 2018-07-31 20:43:42
○ 2026-03-24 22:35:50

○A98.124.199.512016-03-07 → 2016-06-25 · 4 obs

● 2016-03-07 00:56:42
● 2016-06-25 19:38:52
○ 2017-02-12 09:54:20
○ 2026-03-24 22:35:50

○CNAMEhdredirect-lb3-890977680.us-east-1.elb.amazonaws.com2018-07-31 → 2018-07-31 · 2 obs

● 2018-07-31 20:43:42
○ 2026-03-24 22:35:50

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	c.gtld-servers.net, g.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net...	-
weddingtobe.com	nsg1.namebrightdns.com, nsg2.namebrightdns.com	20 records

✅ Authoritative Response

Server:44.220.149.224

NS records: nsg1.namebrightdns.com, nsg2.namebrightdns.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for weddingtobe.com (unsigned zone)

⏱️ Timing

Total: 212ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`13.223.25.84, 54.243.117.197`
AAAA	2	`2600:1f18:4ae:c606:78d4:4260:db4e:aeee, 2600:1f18:4ae:c605:dd5d:b838:5816:d7fb`
NS	2	`nsg1.namebrightdns.com, nsg2.namebrightdns.com`
TXT	2	`afternic-verification-G9G3tM8T8EwEizzPzj, v=spf1 -all`
SOA	1	`ns1.namebrightdns.com dns.namebright.com`

📌 Glue Records Collected

Total: 20

Out-of-bailiwick: 20 (nsg1.namebrightdns.com, nsg1.namebrightdns.com, nsg1.namebrightdns.com...)

Analysis

IP Addresses

weddingtobe.com resolves to four IPs: 2600:1f18:4ae:c605:dd5d:b838:5816:d7fb, 2600:1f18:4ae:c606:78d4:4260:db4e:aeee, 13.223.25.84 and 54.243.117.197.

Other host names such as img.photo.mcthemes.com, mx.dutchlandscaping.com, 209-20-67-146.static.cloud-ips.com, dogpay.net and zypxyr.free2.vegao.com share IP numbers with weddingtobe.com.

Name Servers

weddingtobe.com is delegated to three name servers: ns1.namebrightdns.com, nsg1.namebrightdns.com and nsg2.namebrightdns.com.

At least part of the name servers for weddingtobe.com are shared with other domains, for instance mx.justriver.com, datalivemarketing.com, vismanet.com, tbw.com and tradehunk.com.

These name servers are often used together with ns2.namebrightdns.com, domain-for-sale.hugedomainsdns.com and forsale.hugedomainsdns.com.

Host names with eight IP numbers:

nsg1.namebrightdns.com points to: 2600:1f18:683a:ae1a:5c5e:bc55:1478:cf93, 2600:1f18:683a:ae1a:e5a9:8ee2:a408:496a, 2600:1f18:683a:ae1a:e842:8110:107c:b494, 2600:1f18:683a:ae1b:a136:1971:9598:5d4a, 13.221.125.168, 23.22.234.151, 44.220.149.224 and 54.90.222.89.

nsg2.namebrightdns.com points to: 2600:1f18:683a:ae1a:e1f7:fcf3:dce8:5758, 2600:1f18:683a:ae1b:130f:6e59:4e36:8c1e, 2600:1f18:683a:ae1b:9806:d504:f0e4:26c, 2600:1f18:683a:ae1b:eda8:cb11:b8f:c1fe, 3.82.54.251, 3.85.217.230, 3.89.204.207 and 98.93.89.251.

Host names with six IP numbers:

ns1.namebrightdns.com points to: 2600:1f18:683a:ae1a:aa86:dc69:2f3:5dbe, 2600:1f18:683a:ae1b:3376:e04f:851f:406c, 2600:1f18:683a:ae1b:a510:c365:d06a:e73a, 52.91.47.137, 54.92.199.119 and 98.83.163.23.

weddingtobe.com - robtex.com

weddingtobe.com

com

Same first word

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

📌 Glue Records Collected

Analysis

IP Addresses

Name Servers

`weddingtobe.com`

`com`