guildsec.com - dns.ninja

`guildsec.com`

DNSSEC	⚠️ Not signed
A	104.199.157.252^{🇹🇼 Google104.199.144.0/20}
		PTR	`252.157.199.104.bc.googleusercontent.com`
NS	`ns1.techtools.ph` ⭐
		A	174.138.16.47^{🇸🇬 DIGITALOCEAN174.138.16.0/20 DigitalOcean}
NS	`ns2.techtools.ph`
		A	143.198.222.84^{🇸🇬 DIGITALOCEAN143.198.208.0/20 DigitalOcean}
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c17::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bl-in-f26.1e100.net`
		A	192.178.218.27^{🇺🇸 Google192.178.218.0/24}
			PTR	`yuiadtq-in-f27.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.26^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f26.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c23::1a^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f26.1e100.net`
		A	172.253.157.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f27.1e100.net`
TXT	`v=spf1 include:_spf.google.com ~all`
SOA	`ns1.techtools.ph`info@techtools.ph 2025-01-03 #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=1781963790

Same first word

guildsec.net

guildsec.com

Similar names

clsguide.com

celugids.lv

DNS History

23 records (8 active, 15 former)

○NSdns1.name-services.com2015-05-22 → 2016-04-05 · 4 obs

● 2015-05-22 01:14:36
● 2016-04-05 18:41:50
○ 2017-02-18 22:20:18
○ 2026-06-20 14:26:46

○NSdns2.name-services.com2015-05-22 → 2016-04-05 · 4 obs

● 2015-05-22 01:14:36
● 2016-04-05 18:41:50
○ 2017-02-18 22:20:18
○ 2026-06-20 14:26:46

○NSdns3.name-services.com2015-05-22 → 2016-04-05 · 4 obs

● 2015-05-22 01:14:36
● 2016-04-05 18:41:50
○ 2017-02-18 22:20:18
○ 2026-06-20 14:26:46

○NSdns4.name-services.com2015-05-22 → 2016-04-05 · 4 obs

● 2015-05-22 01:14:36
● 2016-04-05 18:41:50
○ 2017-02-18 22:20:18
○ 2026-06-20 14:26:46

○NSdns5.name-services.com2015-05-22 → 2016-04-05 · 4 obs

● 2015-05-22 01:14:36
● 2016-04-05 18:41:50
○ 2017-02-18 22:20:18
○ 2026-06-20 14:26:46

○NSns1.jp01.tmd.cloud2017-02-18 → 2017-02-18 · 4 obs

○ 2016-04-05 18:41:50
● 2017-02-18 22:20:18
○ 2020-03-16 11:58:20
○ 2026-06-20 14:26:46

○NSns1.jp02new.tmd.cloud2020-03-16 → 2020-11-17 · 5 obs

○ 2017-02-18 22:20:18
● 2020-03-16 11:58:20
● 2020-11-17 14:58:08
○ 2026-02-17 10:37:46
○ 2026-06-20 14:26:46

●NSns1.techtools.ph2026-02-17 → 2026-06-20 · 3 obs

○ 2020-11-17 14:58:08
● 2026-02-17 10:37:46
● 2026-06-20 14:26:46

○NSns2.jp01.tmd.cloud2017-02-18 → 2017-02-18 · 4 obs

○ 2016-04-05 18:41:50
● 2017-02-18 22:20:18
○ 2020-03-16 11:58:20
○ 2026-06-20 14:26:46

○NSns2.jp02new.tmd.cloud2020-03-16 → 2020-11-17 · 5 obs

○ 2017-02-18 22:20:18
● 2020-03-16 11:58:20
● 2020-11-17 14:58:08
○ 2026-02-17 10:37:46
○ 2026-06-20 14:26:46

●NSns2.techtools.ph2026-02-17 → 2026-06-20 · 3 obs

○ 2020-11-17 14:58:08
● 2026-02-17 10:37:46
● 2026-06-20 14:26:46

●MXalt1.aspmx.l.google.com2015-05-22 → 2026-06-20 · 2 obs

● 2015-05-22 01:14:36
● 2026-06-20 14:26:46

●MXalt2.aspmx.l.google.com2017-02-18 → 2026-06-20 · 3 obs

○ 2016-04-05 18:41:50
● 2017-02-18 22:20:18
● 2026-06-20 14:26:46

●MXalt3.aspmx.l.google.com2017-02-18 → 2026-06-20 · 3 obs

○ 2016-04-05 18:41:50
● 2017-02-18 22:20:18
● 2026-06-20 14:26:46

●MXalt4.aspmx.l.google.com2017-02-18 → 2026-06-20 · 3 obs

○ 2016-04-05 18:41:50
● 2017-02-18 22:20:18
● 2026-06-20 14:26:46

●MXaspmx.l.google.com2015-05-22 → 2026-06-20 · 2 obs

● 2015-05-22 01:14:36
● 2026-06-20 14:26:46

○MXaspmx2.googlemail.com2015-05-22 → 2016-04-05 · 4 obs

● 2015-05-22 01:14:36
● 2016-04-05 18:41:50
○ 2017-02-18 22:20:18
○ 2026-06-20 14:26:46

○MXaspmx3.googlemail.com2015-05-22 → 2016-04-05 · 4 obs

● 2015-05-22 01:14:36
● 2016-04-05 18:41:50
○ 2017-02-18 22:20:18
○ 2026-06-20 14:26:46

●A104.199.157.2522026-02-17 → 2026-06-20 · 3 obs

○ 2020-11-17 14:58:08
● 2026-02-17 10:37:46
● 2026-06-20 14:26:46

○A222.127.201.2222016-01-04 → 2016-04-05 · 5 obs

○ 2015-10-24 18:07:40
● 2016-01-04 06:33:36
● 2016-04-05 18:41:50
○ 2017-02-18 22:20:18
○ 2026-06-20 14:26:46

○A222.127.206.42015-05-22 → 2015-10-24 · 4 obs

● 2015-05-22 01:14:36
● 2015-10-24 18:07:40
○ 2016-01-04 06:33:36
○ 2026-06-20 14:26:46

○A45.32.255.1502020-03-16 → 2020-11-17 · 5 obs

○ 2017-02-18 22:20:18
● 2020-03-16 11:58:20
● 2020-11-17 14:58:08
○ 2026-02-17 10:37:46
○ 2026-06-20 14:26:46

○A45.32.32.602017-02-18 → 2017-02-18 · 4 obs

○ 2016-04-05 18:41:50
● 2017-02-18 22:20:18
○ 2020-03-16 11:58:20
○ 2026-06-20 14:26:46

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	c.gtld-servers.net, j.gtld-servers.net, i.gtld-servers.net, h.gtld-servers.net...	-
guildsec.com	ns2.techtools.ph, ns1.techtools.ph	-

✅ Authoritative Response

Server:174.138.16.47

NS records: ns2.techtools.ph, ns1.techtools.ph

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for guildsec.com (unsigned zone)

⏱️ Timing

Total: 2267ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`104.199.157.252`
NS	2	`ns2.techtools.ph, ns1.techtools.ph`
MX	5	`alt2.aspmx.l.google.com (pri: 5), aspmx.l.google.com (pri: 1)...`
TXT	1	`v=spf1 include:_spf.google.com ~all`
SOA	1	`ns1.techtools.ph info.techtools.ph`

Analysis

IP Addresses

guildsec.com resolves to just one IP address, 104.199.157.252.

Other host names, among them irsiscorp.com and 252.157.199.104.bc.googleusercontent.com, have IP numbers in common with guildsec.com.

Name Servers

guildsec.com has two authoritative name servers — ns1.techtools.ph and ns2.techtools.ph.

guildsec.com shares its NS records with other domains, for example cristinaresearch.org, cct.org.ph, bankard.com and two others.

At least some of guildsec.com's name servers are shared with other domains, for example ph.wegen-energy.com, rcbccredit.com, cristinatravel.net and two more.

It is common for these name servers to be used in conjunction with the name servers cp.techtools.ph, ns01.techtools.ph and ns02.techtools.ph.

Each of ns1.techtools.ph and ns2.techtools.ph has one IP address: ns1.techtools.ph uses 174.138.16.47 and ns2.techtools.ph uses 143.198.222.84.

Mail Servers

guildsec.com has five mail servers, which are aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

There is at least a partial MX overlap between guildsec.com and other domains, including redtopnet.com, ns500754.ns500754.ns500754.ns500754.ns500742.ns500742.ns500705.ns500671.ns500704.ns500666.ns500291.ns500291.ns500131.lustychickser.com, ns500758.ns500698.ns500698.ns500698.ns500698.ns500735.ns500736.ns500698.ns500576.ns500708.ns500576.ns500576.ns500686.ns500652.ns500619.ns500619.trackreceptor.com and two others.

These mail servers tend to appear in combination with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.

Host names that have two IP addresses:

aspmx.l.google.com resolves to 192.178.218.27 and 2607:f8b0:4004:c17::1a.

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

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

alt3.aspmx.l.google.com resolves to 192.178.223.26 and 2a00:1450:4009:c0f::1a.

alt4.aspmx.l.google.com resolves to 172.253.157.27 and 2a00:1450:400c:c23::1a.