reactcom.net - dns.ninja

πŸ›‘οΈDomain Reputation CheckBlocklist, phishing & malware statusβ†’

reactcom.net

net

DNS History

16 records (8 active, 8 former)

NSns1.dns-parking.comns2.dns-parking.comMXmx1.hostinger.commx2.hostinger.comA191.101.104.235212.1.212.1582a02:4780:1e:c04d:b82:e3e8:32f7:d5c52a02:4780:22:e28:c08b:693c:662e:d2be191.101.104.36191.96.144.76195.200.9.622a02:4780:21:417d:5ee2:548c:6bcd:ab742a02:4780:22:3597:c6dd:a106:f31d:37342a02:4780:25:122b:5b02:679:46f9:75d92a02:4780:35:7775:abf7:b497:c551:1d9591.108.103.236
●NSns1.dns-parking.com2026-09-09 β†’ 2026-09-20 Β· 2 obs
● 2026-09-09 12:27:36
● 2026-09-20 09:04:16
●NSns2.dns-parking.com2026-09-09 β†’ 2026-09-20 Β· 2 obs
● 2026-09-09 12:27:36
● 2026-09-20 09:04:16
●MXmx1.hostinger.com2026-09-09 β†’ 2026-09-20 Β· 2 obs
● 2026-09-09 12:27:36
● 2026-09-20 09:04:16
●MXmx2.hostinger.com2026-09-09 β†’ 2026-09-20 Β· 2 obs
● 2026-09-09 12:27:36
● 2026-09-20 09:04:16
●A191.101.104.2352026-09-19 β†’ 2026-09-20 Β· 3 obs
β—‹ 2026-09-18 08:10:16
● 2026-09-19 22:58:18
● 2026-09-20 09:04:16
β—‹A191.101.104.362026-09-18 β†’ 2026-09-18 Β· 4 obs
β—‹ 2026-09-09 12:27:36
● 2026-09-18 08:10:16
β—‹ 2026-09-19 22:58:18
β—‹ 2026-09-20 09:04:16
β—‹A191.96.144.762026-09-18 β†’ 2026-09-18 Β· 4 obs
β—‹ 2026-09-09 12:27:36
● 2026-09-18 08:10:16
β—‹ 2026-09-19 22:58:18
β—‹ 2026-09-20 09:04:16
β—‹A195.200.9.622026-09-09 β†’ 2026-09-09 Β· 3 obs
● 2026-09-09 12:27:36
β—‹ 2026-09-18 08:10:16
β—‹ 2026-09-20 09:04:16
●A212.1.212.1582026-09-19 β†’ 2026-09-20 Β· 3 obs
β—‹ 2026-09-18 08:10:16
● 2026-09-19 22:58:18
● 2026-09-20 09:04:16
●A2a02:4780:1e:c04d:b82:e3e8:32f7:d5c52026-09-19 β†’ 2026-09-20 Β· 3 obs
β—‹ 2026-09-18 08:10:16
● 2026-09-19 22:58:18
● 2026-09-20 09:04:16
β—‹A2a02:4780:21:417d:5ee2:548c:6bcd:ab742026-09-18 β†’ 2026-09-18 Β· 4 obs
β—‹ 2026-09-09 12:27:36
● 2026-09-18 08:10:16
β—‹ 2026-09-19 22:58:18
β—‹ 2026-09-20 09:04:16
β—‹A2a02:4780:22:3597:c6dd:a106:f31d:37342026-09-18 β†’ 2026-09-18 Β· 4 obs
β—‹ 2026-09-09 12:27:36
● 2026-09-18 08:10:16
β—‹ 2026-09-19 22:58:18
β—‹ 2026-09-20 09:04:16
●A2a02:4780:22:e28:c08b:693c:662e:d2be2026-09-19 β†’ 2026-09-20 Β· 3 obs
β—‹ 2026-09-18 08:10:16
● 2026-09-19 22:58:18
● 2026-09-20 09:04:16
β—‹A2a02:4780:25:122b:5b02:679:46f9:75d92026-09-09 β†’ 2026-09-09 Β· 3 obs
● 2026-09-09 12:27:36
β—‹ 2026-09-18 08:10:16
β—‹ 2026-09-20 09:04:16
β—‹A2a02:4780:35:7775:abf7:b497:c551:1d952026-09-09 β†’ 2026-09-09 Β· 3 obs
● 2026-09-09 12:27:36
β—‹ 2026-09-18 08:10:16
β—‹ 2026-09-20 09:04:16
β—‹A91.108.103.2362026-09-09 β†’ 2026-09-09 Β· 3 obs
● 2026-09-09 12:27:36
β—‹ 2026-09-18 08:10:16
β—‹ 2026-09-20 09:04:16

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
netg.gtld-servers.net, h.gtld-servers.net, f.gtld-servers.net, j.gtld-servers.net...-
reactcom.netns1.dns-parking.com, ns2.dns-parking.com-

βœ… Authoritative Response

Server:162.159.24.201

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

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

Root DNSKEY fetch failed: Error: connect EADDRNOTAVAIL 198.41.0.4:53 - Local (0.0.0.0:0)

⏱️ Timing

Total: 2424ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A292.112.198.98, 77.37.76.143
AAAA22a02:4780:50:4e24:3999:5cf0:fd95:e24e, 2a02:4780:4e:6db2:2e2f:4d2b:16cc:a48d
NS2ns2.dns-parking.com, ns1.dns-parking.com
MX2mx1.hostinger.com (pri: 5), mx2.hostinger.com (pri: 10)
TXT1v=spf1 include:_spf.mail.hostinger.com ~
SOA1ns1.dns-parking.com dns.hostinger.com

Analysis

IP Addresses

reactcom.net resolves to four IP addresses: 191.101.104.235, 212.1.212.158, 2a02:4780:1e:c04d:b82:e3e8:32f7:d5c5 and 2a02:4780:22:e28:c08b:693c:662e:d2be.

Name Servers

Two name servers handle the delegation for reactcom.net: ns1.dns-parking.com and ns2.dns-parking.com.

ns1.dns-parking.com and ns2.dns-parking.com both carry two IP addresses. The A records for ns1.dns-parking.com are 162.159.24.201 and 2400:cb00:2049:1::a29f:18c9; the A records for ns2.dns-parking.com are 162.159.25.42 and 2400:cb00:2049:1::a29f:192a.

Mail Servers

reactcom.net uses two mail servers, mx1.hostinger.com and mx2.hostinger.com.

mx1.hostinger.com and mx2.hostinger.com each point to two IP numbers β€” 172.65.182.103 and 2606:4700:90:0:c1f8:f874:2386:b61f β€” making both hosts identical in their DNS resolution.

mx1.hostinger.com along with mx2.hostinger.com each resolve to 2606:4700:90:0:c1f8:f874:2386:b61f IP addresses.

mx1.hostinger.com along with mx2.hostinger.com each resolve to 172.65.182.103 IP addresses.