`emmablue.com`

DNSSEC	⚠️ Not signed
NS	`ns1.netregistry.net` ⭐
		A	13.248.158.180^{🇺🇸 Amazon13.248.144.0/20}
			PTR	`a79764cc55c0ac9c0.awsglobalaccelerator.com`
NS	`ns2.netregistry.net`
		A	75.2.118.134^{🇺🇸 Amazon75.2.112.0/20}
			PTR	`abc65dd9a44b5332f.awsglobalaccelerator.com`
NS	`ns3.netregistry.net`
		A	76.223.26.245^{🇺🇸 Amazon76.223.16.0/20}
			PTR	`a79764cc55c0ac9c0.awsglobalaccelerator.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c17::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bl-in-f26.1e100.net`
		A	142.251.167.26^{🇺🇸 Google142.251.167.0/24}
			PTR	`ww-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.26^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f26.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1a^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f26.1e100.net`
		A	192.178.223.27^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f27.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c23::1b^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f27.1e100.net`
		A	172.253.157.26^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f26.1e100.net`
SOA	`ns1.netregistry.net`dmain@netregistry.net 2022-10-02 #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=1784016767

WOT: SAFE (34/100)

Same first word

emmablue.com

emmablue.co.za

DNS History

11 records (8 active, 3 former)

●NSns1.netregistry.net2020-01-25 → 2026-07-14 · 3 obs

○ 2017-03-19 04:22:04
● 2020-01-25 06:57:46
● 2026-07-14 08:26:10

○NSns1.peakhosting.com.au2015-07-24 → 2017-03-19 · 4 obs

● 2015-07-24 18:52:14
● 2017-03-19 04:22:04
○ 2020-01-25 06:57:46
○ 2026-07-14 08:26:10

●NSns2.netregistry.net2020-01-25 → 2026-07-14 · 3 obs

○ 2017-03-19 04:22:04
● 2020-01-25 06:57:46
● 2026-07-14 08:26:10

○NSns2.peakhosting.com.au2015-07-24 → 2017-03-19 · 4 obs

● 2015-07-24 18:52:14
● 2017-03-19 04:22:04
○ 2020-01-25 06:57:46
○ 2026-07-14 08:26:10

●NSns3.netregistry.net2020-01-25 → 2026-07-14 · 3 obs

○ 2017-03-19 04:22:04
● 2020-01-25 06:57:46
● 2026-07-14 08:26:10

●MXalt1.aspmx.l.google.com2015-07-24 → 2026-07-14 · 2 obs

● 2015-07-24 18:52:14
● 2026-07-14 08:26:10

●MXalt2.aspmx.l.google.com2015-07-24 → 2026-07-14 · 2 obs

● 2015-07-24 18:52:14
● 2026-07-14 08:26:10

●MXalt3.aspmx.l.google.com2015-07-24 → 2026-07-14 · 2 obs

● 2015-07-24 18:52:14
● 2026-07-14 08:26:10

●MXalt4.aspmx.l.google.com2015-07-24 → 2026-07-14 · 2 obs

● 2015-07-24 18:52:14
● 2026-07-14 08:26:10

●MXaspmx.l.google.com2015-07-24 → 2026-07-14 · 2 obs

● 2015-07-24 18:52:14
● 2026-07-14 08:26:10

○A50.87.108.652015-07-24 → 2017-03-19 · 4 obs

● 2015-07-24 18:52:14
● 2017-03-19 04:22:04
○ 2020-01-25 06:57:46
○ 2026-07-14 08:26:10

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	j.gtld-servers.net, a.gtld-servers.net, h.gtld-servers.net, l.gtld-servers.net...	-
emmablue.com	ns3.netregistry.net, ns1.netregistry.net, ns2.netregistry.net	-

✅ Authoritative Response

Server:75.2.118.134

NS records: ns3.netregistry.net, ns1.netregistry.net, ns2.netregistry.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for emmablue.com (unsigned zone)

⏱️ Timing

Total: 1093ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	3	`ns1.netregistry.net, ns2.netregistry.net...`
MX	5	`ALT4.ASPMX.L.GOOGLE.com (pri: 10), ALT1.ASPMX.L.GOOGLE.com (pri: 5)...`
SOA	1	`ns1.netregistry.net dmain.netregistry.ne`

Analysis

Name Servers

DNS for emmablue.com is handled by three authoritative name servers: ns1.netregistry.net, ns2.netregistry.net and ns3.netregistry.net.

The name servers of emmablue.com overlap at least partially with those of other domains — among them yarnsartworkinsilk.com, placehosts.com, gijfc.com and two more.

These name servers are frequently paired with the name servers ns1.domainname.edu.au, ns2.domainname.edu.au, ns3.domainname.edu.au and two others.

ns1.netregistry.net, ns2.netregistry.net and ns3.netregistry.net all have one IP address each — ns1.netregistry.net directs to 13.248.158.180, ns2.netregistry.net directs to 75.2.118.134 and ns3.netregistry.net directs to 76.223.26.245.