`waglebagle.net`

DNSSEC	⚠️ Not signed
A	14.63.216.239^{🇰🇷 KT-NET14.56.0.0/13 Korea Telecom}
NS	`ns1-04.azure-dns.com` ⭐
		A	2603:1061:0:700::4^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-04.azure-dns.com`
		A	13.107.236.4^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-04.azure-dns.com`
NS	`ns2-04.azure-dns.net`
		A	2620:1ec:8ec:700::4^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-04.azure-dns.net`
		A	150.171.21.4^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-04.azure-dns.net`
NS	`ns3-04.azure-dns.org`
		A	2a01:111:4000:700::4^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-04.azure-dns.org`
		A	204.14.183.4^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-04.azure-dns.org`
NS	`ns4-04.azure-dns.info`
		A	2620:1ec:bda:700::4^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-04.azure-dns.info`
		A	208.84.5.4^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-04.azure-dns.info`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c27::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadsk-in-f27.1e100.net`
		A	142.251.163.27^{🇺🇸 Google142.251.163.0/24}
			PTR	`wv-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽²⁰⁾
		A	2800:3f0:4003:c0f::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.27^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f27.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	`aspmx2.googlemail.com`⁽²⁰⁾
		A	2800:3f0:4003:c0f::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.26^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f26.1e100.net`
MX	`aspmx3.googlemail.com`⁽³⁰⁾
		A	2a00:1450:400b:c02::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
MX	`aspmx4.googlemail.com`⁽³⁰⁾
		A	2a00:1450:4009:c0f::1a^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f26.1e100.net`
		A	192.178.223.26^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f26.1e100.net`
MX	`aspmx5.googlemail.com`⁽³⁰⁾
		A	2a00:1450:400c:c23::1b^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f27.1e100.net`
		A	172.253.157.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f27.1e100.net`
TXT	`turingsign=0348E69D-7D0F-86FC-EF27-285105F81317`
SOA	`ns1-04.azure-dns.com`azuredns-hostmaster@microsoft.com serial=1

`net`

	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=1785884009

Same first word

waglebagle.net

waglebagle.co.kr

DNS History

19 records (12 active, 7 former)

○NSns.gabia.co.kr2026-07-03 → 2026-08-04 · 2 obs

○ 2026-07-03 22:37:54
○ 2026-08-04 22:55:00

○NSns.gabia.net2026-07-03 → 2026-08-04 · 2 obs

○ 2026-07-03 22:37:54
○ 2026-08-04 22:55:00

○NSns.kt-idc.com2015-07-15 → 2020-04-01 · 4 obs

● 2015-07-15 11:47:18
● 2020-04-01 09:12:18
○ 2026-07-03 22:37:54
○ 2026-08-04 22:55:00

●NSns1-04.azure-dns.com2026-07-03 → 2026-08-04 · 3 obs

○ 2020-04-01 09:12:18
● 2026-07-03 22:37:54
● 2026-08-04 22:55:00

○NSns1.gabia.co.kr2026-07-03 → 2026-08-04 · 2 obs

○ 2026-07-03 22:37:54
○ 2026-08-04 22:55:00

●NSns2-04.azure-dns.net2026-07-03 → 2026-08-04 · 3 obs

○ 2020-04-01 09:12:18
● 2026-07-03 22:37:54
● 2026-08-04 22:55:00

○NSns2.kt-idc.com2015-07-15 → 2020-04-01 · 4 obs

● 2015-07-15 11:47:18
● 2020-04-01 09:12:18
○ 2026-07-03 22:37:54
○ 2026-08-04 22:55:00

●NSns3-04.azure-dns.org2026-07-03 → 2026-08-04 · 3 obs

○ 2020-04-01 09:12:18
● 2026-07-03 22:37:54
● 2026-08-04 22:55:00

●NSns4-04.azure-dns.info2026-07-03 → 2026-08-04 · 3 obs

○ 2020-04-01 09:12:18
● 2026-07-03 22:37:54
● 2026-08-04 22:55:00

●MXalt1.aspmx.l.google.com2015-07-15 → 2026-08-04 · 2 obs

● 2015-07-15 11:47:18
● 2026-08-04 22:55:00

●MXalt2.aspmx.l.google.com2015-07-15 → 2026-08-04 · 2 obs

● 2015-07-15 11:47:18
● 2026-08-04 22:55:00

●MXaspmx.l.google.com2015-07-15 → 2026-08-04 · 2 obs

● 2015-07-15 11:47:18
● 2026-08-04 22:55:00

●MXaspmx2.googlemail.com2015-07-15 → 2026-08-04 · 2 obs

● 2015-07-15 11:47:18
● 2026-08-04 22:55:00

●MXaspmx3.googlemail.com2015-07-15 → 2026-08-04 · 2 obs

● 2015-07-15 11:47:18
● 2026-08-04 22:55:00

●MXaspmx4.googlemail.com2015-07-15 → 2026-08-04 · 2 obs

● 2015-07-15 11:47:18
● 2026-08-04 22:55:00

●MXaspmx5.googlemail.com2015-07-15 → 2026-08-04 · 2 obs

● 2015-07-15 11:47:18
● 2026-08-04 22:55:00

○A121.156.55.352015-07-15 → 2016-11-27 · 4 obs

● 2015-07-15 11:47:18
● 2016-11-27 12:14:16
○ 2020-04-01 09:12:18
○ 2026-08-04 22:55:00

○A14.63.212.612020-04-01 → 2020-04-01 · 4 obs

○ 2016-11-27 12:14:16
● 2020-04-01 09:12:18
○ 2026-07-03 22:37:54
○ 2026-08-04 22:55:00

●A14.63.216.2392026-07-03 → 2026-08-04 · 3 obs

○ 2020-04-01 09:12:18
● 2026-07-03 22:37:54
● 2026-08-04 22:55:00

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
net	m.gtld-servers.net, k.gtld-servers.net, b.gtld-servers.net, f.gtld-servers.net...	-
waglebagle.net	ns1-04.azure-dns.com, ns2-04.azure-dns.net, ns3-04.azure-dns.org, ns4-04.azure-dns.info	2 records

✅ Authoritative Response

Server:150.171.21.4

NS records: ns1-04.azure-dns.com, ns2-04.azure-dns.net, ns3-04.azure-dns.org, ns4-04.azure-dns.info

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for waglebagle.net (unsigned zone)

⏱️ Timing

Total: 631ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`14.63.216.239`
NS	4	`ns1-04.azure-dns.com, ns2-04.azure-dns.net...`
MX	7	`aspmx5.googlemail.com (pri: 30), aspmx3.googlemail.com (pri: 30)...`
TXT	1	`turingsign=0348E69D-7D0F-86FC-EF27-28510`
SOA	1	`ns1-04.azure-dns.com azuredns-hostmaster`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns2-04.azure-dns.net, ns2-04.azure-dns.net)

Analysis

IP Addresses

waglebagle.net resolves to just one IP address, 14.63.216.239.

Name Servers

The NS records for waglebagle.net point to four name servers: ns1-04.azure-dns.com, ns4-04.azure-dns.info, ns2-04.azure-dns.net and ns3-04.azure-dns.org.

There is at least partial name server overlap between waglebagle.net and other domains — microsoft-online.us, aviationmessage.com, ns1.inet.edu.ar and two more among them.

All four hostnames — ns1-04.azure-dns.com, ns4-04.azure-dns.info, ns2-04.azure-dns.net and ns3-04.azure-dns.org — resolve to two IP numbers apiece: ns1-04.azure-dns.com to 13.107.236.4 and 2603:1061:0:700::4; ns4-04.azure-dns.info to 208.84.5.4 and 2620:1ec:bda:700::4; ns2-04.azure-dns.net to 150.171.21.4 and 2620:1ec:8ec:700::4; ns3-04.azure-dns.org to 204.14.183.4 and 2a01:111:4000:700::4.

Mail Servers

waglebagle.net accepts email via 7 mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com and 4 other.

There is at least a partial MX overlap between waglebagle.net and other domains, including cityguesthouse.com, jcgb.org, franrodriguez.net and two others.

These mail servers tend to appear in combination with mail servers alt2.aspmx.l.google.com, aspmx.l.google.com, alt1.aspmx.l.google.com and 3 others.

Host names that have two IP addresses:

aspmx2.googlemail.com points to 108.177.123.26 and 2800:3f0:4003:c0f::1a.

aspmx3.googlemail.com points to 172.253.116.27 and 2a00:1450:400b:c02::1a.

aspmx4.googlemail.com points to 192.178.223.26 and 2a00:1450:4009:c0f::1a.

aspmx5.googlemail.com points to 172.253.157.27 and 2a00:1450:400c:c23::1b.

aspmx.l.google.com points to 142.251.163.27 and 2607:f8b0:4004:c27::1b.

alt1.aspmx.l.google.com points to 108.177.123.27 and 2800:3f0:4003:c0f::1b.

alt2.aspmx.l.google.com points to 172.253.116.26 and 2a00:1450:400b:c02::1b.