onalertrobot.com - dns.ninja

`onalertrobot.com`

DNSSEC	⚠️ Not signed
A	167.235.64.189^{🇩🇪 Hetzner167.235.0.0/16 HETZNER-DC}
		PTR	`static.189.64.235.167.clients.your-server.de`
NS	`ns1.first-ns.de` ⭐
		A	2a01:4f8:0:a101::a:1^{🇩🇪 Hetzner2a01:4f8::/32 HETZNER-IPv6-BLK}
			PTR	`ns1.first-ns.de`
		A	213.239.242.238^{🇩🇪 Hetzner213.239.192.0/18 HETZNER-RZ-NBG-BLK2}
			PTR	`ns1.first-ns.de`
NS	`robotns2.second-ns.de`
		A	2a01:4f8:0:1::5ddc:2^{🇩🇪 Hetzner2a01:4f8::/32 HETZNER-IPv6-BLK}
			PTR	`robotns2.second-ns.de`
		A	213.133.100.103^{🇩🇪 Hetzner213.133.96.0/19 HETZNER-RZ-NBG-BLK1}
			PTR	`robotns2.second-ns.de`
NS	`robotns3.second-ns.com`
		A	2001:67c:192c::add:a3^{🇩🇪 NORIS-NETWORK2001:67c:192c::/48}
			PTR	`robotns3.second-ns.com`
		A	193.47.99.3^{🇩🇪 NORIS-NETWORK193.47.99.0/24}
			PTR	`robotns3.second-ns.com`
MX	`mx.yandex.net` ⭐
		A	2a02:6b8::311^{🇷🇺 TELETECH2a02:6b8::/32 Yandex network}
			PTR	`mxfront.stable.qloud-b.yandex.net`
		A	77.88.21.249^{🇷🇺 TELETECH77.88.0.0/18 Yandex enterprise network}
			PTR	`mxfront.stable.qloud-b.yandex.net`
TXT	`v=spf1 mx a ip4:167.235.64.189/32 include:yandex.net ?all`
SOA	`ns1.first-ns.de`dns@hetzner.com 2025-12-16 #0

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

Same first word

onalertrobot.com

DNS History

6 records (5 active, 1 former)

●NSns1.first-ns.de2019-12-15 → 2026-08-04 · 2 obs

● 2019-12-15 21:44:58
● 2026-08-04 04:04:26

●NSrobotns2.second-ns.de2019-12-15 → 2026-08-04 · 2 obs

● 2019-12-15 21:44:58
● 2026-08-04 04:04:26

●NSrobotns3.second-ns.com2019-12-15 → 2026-08-04 · 2 obs

● 2019-12-15 21:44:58
● 2026-08-04 04:04:26

●MXmx.yandex.net2019-12-15 → 2026-08-04 · 2 obs

● 2019-12-15 21:44:58
● 2026-08-04 04:04:26

○A116.203.26.1892019-12-15 → 2019-12-15 · 3 obs

● 2019-12-15 21:44:58
○ 2026-04-05 11:44:12
○ 2026-08-04 04:04:26

●A167.235.64.1892026-04-05 → 2026-08-04 · 3 obs

○ 2019-12-15 21:44:58
● 2026-04-05 11:44:12
● 2026-08-04 04:04:26

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, m.gtld-servers.net, k.gtld-servers.net, b.gtld-servers.net...	-
onalertrobot.com	ns1.first-ns.de, robotns2.second-ns.de, robotns3.second-ns.com	2 records

✅ Authoritative Response

Server:213.239.242.238

NS records: ns1.first-ns.de, robotns2.second-ns.de, robotns3.second-ns.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for onalertrobot.com (unsigned zone)

⏱️ Timing

Total: 871ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`167.235.64.189`
NS	3	`robotns3.second-ns.com, ns1.first-ns.de...`
MX	1	`mx.yandex.net (pri: 10)`
TXT	1	`v=spf1 mx a ip4:167.235.64.189/32 includ`
SOA	1	`ns1.first-ns.de dns.hetzner.com`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (robotns3.second-ns.com, robotns3.second-ns.com)

Analysis

IP Addresses

onalertrobot.com has exactly one IP address — 167.235.64.189.

prosystem.gr and static.189.64.235.167.clients.your-server.de are among other host names that share IP numbers with onalertrobot.com.

Name Servers

onalertrobot.com is served by three name servers: robotns3.second-ns.com, ns1.first-ns.de and robotns2.second-ns.de.

The name servers of onalertrobot.com overlap at least partially with those of other domains — among them bramex.de, profiletv.net, tielburger.at and two more.

The name servers hydrogen.ns.hetzner.com, oxygen.ns.hetzner.com and helium.ns.hetzner.de are commonly seen alongside these name servers.

The hostnames robotns3.second-ns.com, ns1.first-ns.de and robotns2.second-ns.de each direct to two IP addresses — robotns3.second-ns.com to 193.47.99.3 and 2001:67c:192c::add:a3, ns1.first-ns.de to 213.239.242.238 and 2a01:4f8:0:a101::a:1, and robotns2.second-ns.de to 213.133.100.103 and 2a01:4f8:0:1::5ddc:2.

Mail Servers

onalertrobot.com uses one mail server — mx.yandex.net.

The mail server setup of onalertrobot.com matches that of other domains such as led-line.pro, citportal.ru, tarifcim.com and two others.

onalertrobot.com partially shares its mail servers with other domains — including heroturko.net, inm.ras.ru, restorange.ru and forex-ratings.com.

mx.yandex.net resolves to two IP numbers — 77.88.21.249 and 2a02:6b8::311.