updatecommand.com - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`updatecommand.com`

DNSSEC	⚠️ Not signed
A	2406:da1e:214:c901:de1:4619:cf23:c131^{🇨🇳 Amazon2406:da1e::/38}
A	2600:1f18:6a07:601:3a2e:6474:85a2:7d3b^{🇺🇸 Amazon2600:1f18:6000::/35 AMAZON EC2 IAD prefix}
A	2600:1f1c:6db:8800:a891:bc12:a756:c828^{🇺🇸 Amazon2600:1f1c:400::/38 AMAZON AWS}
A	2600:1f1c:6db:8801:631:303:9450:bb3a^{🇺🇸 Amazon2600:1f1c:400::/38 AMAZON AWS}
A	2a01:4ff:1f0:dd50::1^{🇩🇪 HETZNER-CLOUD3-AS2a01:4ff:100::/40 HETZNER-IPv6-BLK}
A	2a05:d014:179b:c400:2fc6:8141:276a:b7e9^{🇩🇪 Amazon2a05:d014:1400::/38}
A	2a05:d018:1d22:800:1042:b3aa:b044:f52b^{🇮🇪 Amazon2a05:d018:1000::/36 EC2 DUB Prefix}
A	2a05:d018:1d22:801:7ca6:aafe:5648:9460^{🇮🇪 Amazon2a05:d018:1000::/36 EC2 DUB Prefix}
A	5.78.156.59^{🇺🇸 HETZNER-CLOUD3-AS5.78.156.0/24}
A	5.161.47.86^{🇺🇸 HETZNER-CLOUD2-AS5.161.47.0/24}
A	5.161.230.87^{🇺🇸 HETZNER-CLOUD2-AS5.161.230.0/24}
A	46.62.237.138^{🇩🇪 Hetzner46.62.128.0/17 HETZNER-DC}
A	76.223.91.20^{🇺🇸 Amazon76.223.80.0/20}
A	195.201.128.179^{🇩🇪 Hetzner195.201.0.0/16 HETZNER-DC}
NS	`ns1.dns-redirect.com` ⭐
		A	5.161.47.86^{🇺🇸 HETZNER-CLOUD2-AS5.161.47.0/24}
			PTR	`static.86.47.161.5.clients.your-server.de`
		A	5.161.230.87^{🇺🇸 HETZNER-CLOUD2-AS5.161.230.0/24}
			PTR	`static.87.230.161.5.clients.your-server.de`
		A	195.201.128.179^{🇩🇪 Hetzner195.201.0.0/16 HETZNER-DC}
			PTR	`static.179.128.201.195.clients.your-server.de`
NS	`ns2.dns-redirect.com`
		A	76.223.91.20^{🇺🇸 Amazon76.223.80.0/20}
			PTR	`ad988eeb126877ff9.awsglobalaccelerator.com`
		A	166.117.68.124^{🇺🇸 Amazon166.117.64.0/20}
			PTR	`ad988eeb126877ff9.awsglobalaccelerator.com`
TXT	`95b3a950-315c-45b8-937a-b865ebeb043a`
TXT	`afternic-verification-aGHTsEA2nLa7KRqzmJySAx`
TXT	`abuse-report=mailto:abuse@redirhub.com`
SOA	`ns1.dns-redirect.com`admin@dns.com 2024-07-29 #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=1789285133

Same first word

updatecommand.com

Previous names

Next names

DNS History

28 records (16 active, 12 former)

○NSns-1294.awsdns-33.org2017-02-09 → 2019-04-05 · 4 obs

● 2017-02-09 21:10:32
● 2019-04-05 19:52:46
○ 2026-08-24 19:40:48
○ 2026-09-13 07:42:32

○NSns-1788.awsdns-31.co.uk2017-02-09 → 2019-04-05 · 4 obs

● 2017-02-09 21:10:32
● 2019-04-05 19:52:46
○ 2026-08-24 19:40:48
○ 2026-09-13 07:42:32

○NSns-196.awsdns-24.com2017-02-09 → 2019-04-05 · 4 obs

● 2017-02-09 21:10:32
● 2019-04-05 19:52:46
○ 2026-08-24 19:40:48
○ 2026-09-13 07:42:32

○NSns-885.awsdns-46.net2017-02-09 → 2019-04-05 · 4 obs

● 2017-02-09 21:10:32
● 2019-04-05 19:52:46
○ 2026-08-24 19:40:48
○ 2026-09-13 07:42:32

●NSns1.dns-redirect.com2026-08-24 → 2026-09-13 · 3 obs

○ 2019-04-05 19:52:46
● 2026-08-24 19:40:48
● 2026-09-13 07:42:32

●NSns2.dns-redirect.com2026-08-24 → 2026-09-13 · 3 obs

○ 2019-04-05 19:52:46
● 2026-08-24 19:40:48
● 2026-09-13 07:42:32

○MXin1-smtp.messagingengine.com2017-02-09 → 2019-04-05 · 4 obs

● 2017-02-09 21:10:32
● 2019-04-05 19:52:46
○ 2026-08-24 19:40:48
○ 2026-09-13 07:42:32

○MXin2-smtp.messagingengine.com2017-02-09 → 2019-04-05 · 4 obs

● 2017-02-09 21:10:32
● 2019-04-05 19:52:46
○ 2026-08-24 19:40:48
○ 2026-09-13 07:42:32

●A195.201.128.1792026-08-24 → 2026-09-13 · 2 obs

● 2026-08-24 19:40:48
● 2026-09-13 07:42:32

○A2406:da1e:214:c901:9c13:e7d4:fc52:b9252026-08-24 → 2026-08-24 · 3 obs

● 2026-08-24 19:40:48
○ 2026-09-12 23:43:40
○ 2026-09-13 07:42:32

●A2406:da1e:214:c901:de1:4619:cf23:c1312026-09-12 → 2026-09-13 · 3 obs

○ 2026-08-24 19:40:48
● 2026-09-12 23:43:40
● 2026-09-13 07:42:32

●A2600:1f18:6a07:601:3a2e:6474:85a2:7d3b2026-08-24 → 2026-09-13 · 2 obs

● 2026-08-24 19:40:48
● 2026-09-13 07:42:32

●A2600:1f1c:6db:8800:a891:bc12:a756:c8282026-09-13 → 2026-09-13 · 3 obs

○ 2026-09-12 23:43:40
● 2026-09-13 07:21:52
● 2026-09-13 07:42:32

○A2600:1f1c:6db:8801:4444:e17e:a296:4fb92026-08-24 → 2026-08-24 · 3 obs

● 2026-08-24 19:40:48
○ 2026-09-12 23:43:40
○ 2026-09-13 07:42:32

●A2600:1f1c:6db:8801:631:303:9450:bb3a2026-09-12 → 2026-09-13 · 3 obs

○ 2026-08-24 19:40:48
● 2026-09-12 23:43:40
● 2026-09-13 07:42:32

○A2a01:4f8:1c1e:d6f1::12026-08-24 → 2026-08-24 · 3 obs

● 2026-08-24 19:40:48
○ 2026-09-13 07:21:52
○ 2026-09-13 07:42:32

●A2a01:4ff:1f0:dd50::12026-08-24 → 2026-09-13 · 2 obs

● 2026-08-24 19:40:48
● 2026-09-13 07:42:32

○A2a01:4ff:f0:5f41::12026-08-24 → 2026-08-24 · 3 obs

● 2026-08-24 19:40:48
○ 2026-09-12 23:43:40
○ 2026-09-13 07:42:32

●A2a05:d014:179b:c400:2fc6:8141:276a:b7e92026-08-24 → 2026-09-13 · 2 obs

● 2026-08-24 19:40:48
● 2026-09-13 07:42:32

●A2a05:d018:1d22:800:1042:b3aa:b044:f52b2026-09-12 → 2026-09-13 · 3 obs

○ 2026-08-24 19:40:48
● 2026-09-12 23:43:40
● 2026-09-13 07:42:32

○A2a05:d018:1d22:800:7a5e:46f1:958d:8ee82026-08-24 → 2026-08-24 · 3 obs

● 2026-08-24 19:40:48
○ 2026-09-12 23:43:40
○ 2026-09-13 07:42:32

○A2a05:d018:1d22:801:539e:fb72:ae5e:57d92026-09-12 → 2026-09-12 · 4 obs

○ 2026-08-24 19:40:48
● 2026-09-12 23:43:40
○ 2026-09-13 07:21:52
○ 2026-09-13 07:42:32

●A2a05:d018:1d22:801:7ca6:aafe:5648:94602026-09-13 → 2026-09-13 · 3 obs

○ 2026-09-12 23:43:40
● 2026-09-13 07:21:52
● 2026-09-13 07:42:32

●A46.62.237.1382026-08-24 → 2026-09-13 · 2 obs

● 2026-08-24 19:40:48
● 2026-09-13 07:42:32

●A5.161.230.872026-08-24 → 2026-09-13 · 2 obs

● 2026-08-24 19:40:48
● 2026-09-13 07:42:32

●A5.161.47.862026-08-24 → 2026-09-13 · 2 obs

● 2026-08-24 19:40:48
● 2026-09-13 07:42:32

●A5.78.156.592026-08-24 → 2026-09-13 · 2 obs

● 2026-08-24 19:40:48
● 2026-09-13 07:42:32

●A76.223.91.202026-08-24 → 2026-09-13 · 2 obs

● 2026-08-24 19:40:48
● 2026-09-13 07:42:32

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	g.gtld-servers.net, e.gtld-servers.net, a.gtld-servers.net, b.gtld-servers.net...	-
updatecommand.com	ns1.dns-redirect.com, ns2.dns-redirect.com	5 records

✅ Authoritative Response

Server:5.161.230.87

NS records: ns1.dns-redirect.com, ns2.dns-redirect.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for updatecommand.com (unsigned zone)

⏱️ Timing

Total: 324ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`5.161.47.86`
AAAA	4	`2a01:4ff:f0:5f41::1, 2a05:d018:1d22:801:7ca6:aafe:5648:9460...`
NS	2	`ns1.dns-redirect.com, ns2.dns-redirect.com`
TXT	3	`afternic-verification-aGHTsEA2nLa7KRqzmJ, 95b3a950-315c-45b8-937a-b865ebeb043a...`
SOA	1	`ns1.dns-redirect.com admin.dns.com`

📌 Glue Records Collected

Total: 5

Out-of-bailiwick: 5 (ns1.dns-redirect.com, ns1.dns-redirect.com, ns1.dns-redirect.com...)

Analysis

IP Addresses

updatecommand.com has 14 IP addresses — 5.78.156.59, 5.161.47.86, 5.161.230.87 and 11 more.

eastendcartoons.com, ziji.studio, sirreileffects.de and two other host names share IP numbers with updatecommand.com.

Name Servers

Two name servers handle the delegation for updatecommand.com: ns1.dns-redirect.com and ns2.dns-redirect.com.

updatecommand.com uses the same name servers as several other domains — among them clairamerica.com, coco1001.online, w88.land and two more.

Hostnames that resolve to three IP addresses:

The hostname ns1.dns-redirect.com points to 5.161.47.86, 5.161.230.87 and 195.201.128.179.

Hostnames that resolve to two IP addresses:

ns2.dns-redirect.com resolves to two addresses: 76.223.91.20 and 166.117.68.124.