gescms.com - dns.ninja

`gescms.com`

DNSSEC	⚠️ Not signed
NS	`b1.gage-johnson.com` ⚠️ Not in zone NS records
		A	2600:9000:a508:7877:de78:593f:c6a9:2d21^{🇺🇸 Amazon2600:9000:a500::/43}
			PTR	`ad348085bae27ec49.dualstack.awsglobalaccelerator.com`
		A	2600:9000:a618:2e79:5422:d2bb:ed3b:a201^{🇺🇸 Amazon2600:9000:a600::/43}
			PTR	`ad348085bae27ec49.dualstack.awsglobalaccelerator.com`
		A	18.216.253.137^{🇺🇸 Amazon18.216.0.0/14 EC2 CMH prefix}
			PTR	`web20.1brandsight.net`
NS	`b2.gage-johnson.com` ⚠️ Not in zone NS records
		A	2600:9000:a508:7877:de78:593f:c6a9:2d21^{🇺🇸 Amazon2600:9000:a500::/43}
			PTR	`ad348085bae27ec49.dualstack.awsglobalaccelerator.com`
		A	2600:9000:a618:2e79:5422:d2bb:ed3b:a201^{🇺🇸 Amazon2600:9000:a600::/43}
			PTR	`ad348085bae27ec49.dualstack.awsglobalaccelerator.com`
		A	3.33.173.124^{🇺🇸 Amazon3.33.160.0/20}
			PTR	`ad348085bae27ec49.awsglobalaccelerator.com`
		A	13.248.248.26^{🇺🇸 Amazon13.248.240.0/20}
			PTR	`ad348085bae27ec49.awsglobalaccelerator.com`

`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=1786390399

Previously MX for

gescms.com

Same first word

gescms.com

Similar names

sescmg.com.br

csgems.com

msgsec.info

gscems.com

smscge.com

secmsg.net

secmsg.com

ssgmce.ac.in

sescmg.com

smscge.net

gmssec.com

smcseg.com

DNS History

8 records (2 active, 6 former)

●NSb1.gage-johnson.com2015-05-24 → 2026-08-10 · 4 obs

● 2015-05-24 11:31:38
○ 2015-10-24 10:11:46
● 2016-01-15 16:24:24
● 2026-08-10 20:00:30

●NSb2.gage-johnson.com2015-05-24 → 2026-08-10 · 4 obs

● 2015-05-24 11:31:38
○ 2015-10-24 10:11:46
● 2016-01-15 16:24:24
● 2026-08-10 20:00:30

○NSv1.gage-johnson.com2015-10-24 → 2015-10-24 · 4 obs

○ 2015-05-24 11:31:38
● 2015-10-24 10:11:46
○ 2016-01-15 16:24:24
○ 2026-08-10 20:00:30

○NSv2.gage-johnson.com2015-10-24 → 2015-10-24 · 4 obs

○ 2015-05-24 11:31:38
● 2015-10-24 10:11:46
○ 2016-01-15 16:24:24
○ 2026-08-10 20:00:30

○MXgescms.com2015-05-24 → 2017-09-27 · 4 obs

● 2015-05-24 11:31:38
● 2017-09-27 11:30:04
○ 2026-04-14 01:31:08
○ 2026-08-10 20:00:30

○A192.237.175.1582016-01-15 → 2017-09-27 · 5 obs

○ 2015-10-24 10:11:46
● 2016-01-15 16:24:24
● 2017-09-27 11:30:04
○ 2026-04-14 01:31:08
○ 2026-08-10 20:00:30

○A216.46.52.2362015-05-24 → 2015-05-24 · 3 obs

● 2015-05-24 11:31:38
○ 2015-10-24 10:11:46
○ 2026-08-10 20:00:30

○A98.142.85.1632015-10-24 → 2015-10-24 · 4 obs

○ 2015-05-24 11:31:38
● 2015-10-24 10:11:46
○ 2016-01-15 16:24:24
○ 2026-08-10 20:00:30

🔍 DNS Trace

Analysis

Name Servers

gescms.com uses two name servers for its delegation: b1.gage-johnson.com and b2.gage-johnson.com.

Hosts pointing to four IP addresses:

b2.gage-johnson.com points to 3.33.173.124, 13.248.248.26, 2600:9000:a508:7877:de78:593f:c6a9:2d21 and 2600:9000:a618:2e79:5422:d2bb:ed3b:a201.

Hosts with three IP address records:

The hostname b1.gage-johnson.com directs to 18.216.253.137, 2600:9000:a508:7877:de78:593f:c6a9:2d21 and 2600:9000:a618:2e79:5422:d2bb:ed3b:a201.

Both b2.gage-johnson.com and b1.gage-johnson.com resolve to 2600:9000:a508:7877:de78:593f:c6a9:2d21 IP addresses each.

Both b2.gage-johnson.com and b1.gage-johnson.com resolve to 2600:9000:a618:2e79:5422:d2bb:ed3b:a201 IP addresses each.