shieldsquare.com - dns.ninja

`shieldsquare.com`

DNSSEC	⚠️ Not signed
A	35.201.111.164^{🇺🇸 Google35.200.0.0/15}
		PTR	`164.111.201.35.bc.googleusercontent.com`
NS	`ns-1351.awsdns-40.org` ⭐
		A	2600:9000:5305:4700::1^{🇺🇸 Amazon2600:9000:5305::/48 - CloudFront}
			PTR	`ns-1351.awsdns-40.org`
		A	205.251.197.71^{🇺🇸 Amazon205.251.197.0/24 prefix}
			PTR	`ns-1351.awsdns-40.org`
NS	`ns-1005.awsdns-61.net`
		A	2600:9000:5303:ed00::1^{🇺🇸 Amazon2600:9000:5303::/48 - CloudFront}
			PTR	`ns-1005.awsdns-61.net`
		A	205.251.195.237^{🇺🇸 Amazon205.251.195.0/24 prefix}
			PTR	`ns-1005.awsdns-61.net`
NS	`ns-1800.awsdns-33.co.uk`
		A	2600:9000:5307:800::1^{🇺🇸 Amazon2600:9000:5307::/48 - CloudFront}
			PTR	`ns-1800.awsdns-33.co.uk`
		A	205.251.199.8^{🇺🇸 Amazon205.251.199.0/24 prefix}
			PTR	`ns-1800.awsdns-33.co.uk`
NS	`ns-505.awsdns-63.com`
		A	2600:9000:5301:f900::1^{🇺🇸 Amazon2600:9000:5301::/48 - CloudFront}
			PTR	`ns-505.awsdns-63.com`
		A	205.251.193.249^{🇺🇸 Amazon205.251.193.0/24 prefix}
			PTR	`ns-505.awsdns-63.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c1b::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`wv-in-f26.1e100.net`
		A	173.194.45.26^{🇺🇸 Google173.194.0.0/16}
			PTR	`yuiadum-in-f26.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::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.27^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f27.1e100.net`
MX	`aspmx3.googlemail.com`⁽³⁰⁾
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
TXT	`google-site-verification=bNThGO4xITsNBdnPlEPzBxmDqqHyQMtdbvBlLYF4QII`
TXT	`v=msv1 t=cf2c3ee4343342bcd0f7114006a42d`
TXT	`v=spf1 include:sendgrid.net include:_spf.google.com include:spf.mandrillapp.c...`
SOA	`ns-1351.awsdns-40.org`awsdns-hostmaster@amazon.com serial=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=1785747292

Same first word

shieldsquare.com

shieldsquare.net

Similar names

squareshield.com

DNS History

19 records (10 active, 9 former)

○NSdorthy.ns.cloudflare.com2016-05-02 → 2016-11-16 · 5 obs

○ 2016-01-14 23:17:32
● 2016-05-02 01:11:04
● 2016-11-16 21:50:22
○ 2026-04-20 01:30:00
○ 2026-08-03 09:19:44

●NSns-1005.awsdns-61.net2026-04-20 → 2026-08-03 · 3 obs

○ 2016-11-16 21:50:22
● 2026-04-20 01:30:00
● 2026-08-03 09:19:44

●NSns-1351.awsdns-40.org2026-04-20 → 2026-08-03 · 3 obs

○ 2016-11-16 21:50:22
● 2026-04-20 01:30:00
● 2026-08-03 09:19:44

●NSns-1800.awsdns-33.co.uk2026-04-20 → 2026-08-03 · 3 obs

○ 2016-11-16 21:50:22
● 2026-04-20 01:30:00
● 2026-08-03 09:19:44

●NSns-505.awsdns-63.com2026-04-20 → 2026-08-03 · 3 obs

○ 2016-11-16 21:50:22
● 2026-04-20 01:30:00
● 2026-08-03 09:19:44

○NSns73.domaincontrol.com2015-09-01 → 2016-01-14 · 4 obs

● 2015-09-01 01:38:00
● 2016-01-14 23:17:32
○ 2016-05-02 01:11:04
○ 2026-08-03 09:19:44

○NSns74.domaincontrol.com2015-09-01 → 2016-01-14 · 4 obs

● 2015-09-01 01:38:00
● 2016-01-14 23:17:32
○ 2016-05-02 01:11:04
○ 2026-08-03 09:19:44

○NSrocky.ns.cloudflare.com2016-05-02 → 2016-11-16 · 5 obs

○ 2016-01-14 23:17:32
● 2016-05-02 01:11:04
● 2016-11-16 21:50:22
○ 2026-04-20 01:30:00
○ 2026-08-03 09:19:44

●MXalt1.aspmx.l.google.com2015-09-01 → 2026-08-03 · 2 obs

● 2015-09-01 01:38:00
● 2026-08-03 09:19:44

●MXalt2.aspmx.l.google.com2015-09-01 → 2026-08-03 · 2 obs

● 2015-09-01 01:38:00
● 2026-08-03 09:19:44

●MXaspmx.l.google.com2015-09-01 → 2026-08-03 · 2 obs

● 2015-09-01 01:38:00
● 2026-08-03 09:19:44

●MXaspmx2.googlemail.com2015-09-01 → 2026-08-03 · 2 obs

● 2015-09-01 01:38:00
● 2026-08-03 09:19:44

●MXaspmx3.googlemail.com2015-09-01 → 2026-08-03 · 2 obs

● 2015-09-01 01:38:00
● 2026-08-03 09:19:44

○A104.131.56.2032015-09-01 → 2016-01-14 · 4 obs

● 2015-09-01 01:38:00
● 2016-01-14 23:17:32
○ 2016-05-02 01:11:04
○ 2026-08-03 09:19:44

○A104.20.86.1632016-05-02 → 2016-11-16 · 5 obs

○ 2016-01-14 23:17:32
● 2016-05-02 01:11:04
● 2016-11-16 21:50:22
○ 2026-04-20 01:30:00
○ 2026-08-03 09:19:44

○A104.20.87.1632016-05-02 → 2016-11-16 · 5 obs

○ 2016-01-14 23:17:32
● 2016-05-02 01:11:04
● 2016-11-16 21:50:22
○ 2026-04-20 01:30:00
○ 2026-08-03 09:19:44

○A2400:cb00:2048:1::6814:56a32016-11-16 → 2016-11-16 · 4 obs

○ 2016-05-02 01:11:04
● 2016-11-16 21:50:22
○ 2026-04-20 01:30:00
○ 2026-08-03 09:19:44

○A2400:cb00:2048:1::6814:57a32016-11-16 → 2016-11-16 · 4 obs

○ 2016-05-02 01:11:04
● 2016-11-16 21:50:22
○ 2026-04-20 01:30:00
○ 2026-08-03 09:19:44

●A35.201.111.1642026-04-20 → 2026-08-03 · 3 obs

○ 2016-11-16 21:50:22
● 2026-04-20 01:30:00
● 2026-08-03 09:19:44

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
shieldsquare.com	ns-505.awsdns-63.com, ns-1005.awsdns-61.net, ns-1800.awsdns-33.co.uk, ns-1351.awsdns-40.org	2 records

✅ Authoritative Response

Server:205.251.197.71

NS records: ns-505.awsdns-63.com, ns-1005.awsdns-61.net, ns-1800.awsdns-33.co.uk, ns-1351.awsdns-40.org

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for shieldsquare.com (unsigned zone)

⏱️ Timing

Total: 363ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`35.201.111.164`
NS	4	`ns-1005.awsdns-61.net, ns-1351.awsdns-40.org...`
MX	5	`aspmx.l.google.com (pri: 10), alt1.aspmx.l.google.com (pri: 20)...`
TXT	3	`google-site-verification=bNThGO4xITsNBdn, v=msv1 t=cf2c3ee4343342bcd0f7114006a42d...`
SOA	1	`ns-1351.awsdns-40.org awsdns-hostmaster.`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns-505.awsdns-63.com, ns-505.awsdns-63.com)

Analysis

IP Addresses

shieldsquare.com points to a single IP number: 35.201.111.164.

164.111.201.35.bc.googleusercontent.com, for instance, is one of the other host names sharing IP numbers with shieldsquare.com.

Name Servers

shieldsquare.com has four authoritative name servers: ns-505.awsdns-63.com, ns-1005.awsdns-61.net, ns-1351.awsdns-40.org and ns-1800.awsdns-33.co.uk.

shieldsquare.com has at least partial name server overlap with other domains, such as mamanoko.jp, aquatech-kyoto.com, boardgamebible.com and two others.

ns-505.awsdns-63.com, ns-1005.awsdns-61.net, ns-1351.awsdns-40.org and ns-1800.awsdns-33.co.uk all point to exactly two IP numbers each: ns-505.awsdns-63.com → 205.251.193.249 and 2600:9000:5301:f900::1; ns-1005.awsdns-61.net → 205.251.195.237 and 2600:9000:5303:ed00::1; ns-1351.awsdns-40.org → 205.251.197.71 and 2600:9000:5305:4700::1; ns-1800.awsdns-33.co.uk → 205.251.199.8 and 2600:9000:5307:800::1.

Mail Servers

Mail for shieldsquare.com is handled by five mail servers, namely aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.

shieldsquare.com shares mail servers — at least in part — with other domains, including maliamills.com, ns500754.ns500754.ns500754.ns500742.ns500688.ns500688.ns500705.ns500678.lusty(0x736c7574)z.com, ns500693.ns500693.ns500734.ns500693.ns500693.ns500734.ns500699.ns500699.ns500699.ns500693.ns500588.ns500693.ns500632.ns500588.ns500588.ns500588.dtrkdll.com and two others.

These mail servers are frequently used alongside mail servers alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 other.

Host names with two IP numbers:

aspmx2.googlemail.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1b.

aspmx3.googlemail.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1b.

aspmx.l.google.com directs traffic to 173.194.45.26 and 2607:f8b0:4004:c1b::1a.

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

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

Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 2800:3f0:4003:c0f::1b IP addresses each.

Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 108.177.123.27 IP addresses each.

Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 2a00:1450:400b:c02::1b IP addresses each.