Must be a valid IPv4 or IPv6 ip address, e.g. 127.0.0.1 or 2001:DB8:0:0:8:800:200C:417A
Basic Info

City: unknown

Region: unknown

Country: IANA Special-Purpose Address

Internet Service Provider: unknown

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:
No discussion about this IP yet. Click above link to make one.
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 242.197.9.222
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 15330
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;242.197.9.222.			IN	A

;; AUTHORITY SECTION:
.			30	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2025020500 1800 900 604800 86400

;; Query time: 35 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Feb 05 18:28:55 CST 2025
;; MSG SIZE  rcvd: 106
Host info
Host 222.9.197.242.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 222.9.197.242.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
186.71.70.219 attackspam
445/tcp 445/tcp 445/tcp...
[2019-05-05/06-30]11pkt,1pt.(tcp)
2019-07-01 03:02:28
185.234.219.89 attack
Rude login attack (6 tries in 1d)
2019-07-01 03:33:59
198.108.66.82 attackspam
1433/tcp 20000/tcp 23/tcp
[2019-05-21/06-30]3pkt
2019-07-01 03:40:01
138.197.111.123 attack
[SunJun3015:17:25.5933962019][:error][pid26388:tid47523395413760][client138.197.111.123:40096][client138.197.111.123]ModSecurity:Accessdeniedwithcode403\(phase2\).Patternmatch"Datanyze"atREQUEST_HEADERS:User-Agent.[file"/usr/local/apache.ea3/conf/modsec_rules/20_asl_useragents.conf"][line"68"][id"337749"][rev"2"][msg"Atomicorp.comWAFRules:Datanyzebotblocked"][severity"ERROR"][hostname"yex-swiss.ch"][uri"/"][unique_id"XRi2ZRnQjmXhtkhIr-U05wAAAAY"][SunJun3015:17:27.7005562019][:error][pid26388:tid47523309262592][client138.197.111.123:55414][client138.197.111.123]ModSecurity:Accessdeniedwithcode403\(phase2\).Patternmatch"Datanyze"atREQUEST_HEADERS:User-Agent.[file"/usr/local/apache.ea3/conf/modsec_rules/20_asl_useragents.conf"][line"68"][id"337749"][rev"2"][msg"Atomicorp.comWAFRules:Datanyzebotblocked"][severity"ERROR"][hostname"yex-swiss.ch"][uri"/"][unique_id"XRi2ZxnQjmXhtkhIr-U06AAAAAE"]
2019-07-01 03:10:37
181.74.96.37 attackspam
2323/tcp 23/tcp
[2019-05-30/06-30]2pkt
2019-07-01 03:29:03
77.40.108.36 attack
2019-06-30T12:25:55.166293MailD postfix/smtpd[8563]: warning: unknown[77.40.108.36]: SASL LOGIN authentication failed: authentication failure
2019-06-30T15:04:13.048689MailD postfix/smtpd[20226]: warning: unknown[77.40.108.36]: SASL LOGIN authentication failed: authentication failure
2019-06-30T16:03:36.923064MailD postfix/smtpd[24316]: warning: unknown[77.40.108.36]: SASL LOGIN authentication failed: authentication failure
2019-07-01 03:36:24
182.48.84.6 attackspambots
Jun 29 09:13:32 mail sshd[29223]: Invalid user dayzs from 182.48.84.6
Jun 29 09:13:32 mail sshd[29223]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.48.84.6
Jun 29 09:13:32 mail sshd[29223]: Invalid user dayzs from 182.48.84.6
Jun 29 09:13:34 mail sshd[29223]: Failed password for invalid user dayzs from 182.48.84.6 port 43594 ssh2
Jun 29 09:17:07 mail sshd[2247]: Invalid user pul from 182.48.84.6
...
2019-07-01 02:56:55
165.22.128.115 attackbots
Jun 30 14:43:24 xtremcommunity sshd\[18027\]: Invalid user deploy from 165.22.128.115 port 45270
Jun 30 14:43:24 xtremcommunity sshd\[18027\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.22.128.115
Jun 30 14:43:26 xtremcommunity sshd\[18027\]: Failed password for invalid user deploy from 165.22.128.115 port 45270 ssh2
Jun 30 14:44:52 xtremcommunity sshd\[18064\]: Invalid user shiny from 165.22.128.115 port 33882
Jun 30 14:44:52 xtremcommunity sshd\[18064\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.22.128.115
...
2019-07-01 02:57:36
121.157.62.179 attackspambots
23/tcp 2323/tcp...
[2019-05-04/06-30]4pkt,2pt.(tcp)
2019-07-01 03:25:42
77.40.59.217 attackbots
$f2bV_matches
2019-07-01 03:10:05
46.105.127.166 attackspambots
30.06.2019 21:16:06 - Wordpress fail 
Detected by ELinOX-ALM
2019-07-01 03:26:25
189.213.24.144 attackbots
Honeypot attack, port: 23, PTR: 189-213-24-144.static.axtel.net.
2019-07-01 03:41:24
49.206.224.31 attackbotsspam
Jun 30 20:04:18 host sshd\[42864\]: Invalid user applmgr from 49.206.224.31 port 49412
Jun 30 20:04:18 host sshd\[42864\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.206.224.31
...
2019-07-01 03:31:07
73.164.13.142 attackspambots
Jun 30 15:17:06 localhost sshd\[10657\]: Invalid user pi from 73.164.13.142 port 56104
Jun 30 15:17:06 localhost sshd\[10659\]: Invalid user pi from 73.164.13.142 port 56106
Jun 30 15:17:06 localhost sshd\[10657\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=73.164.13.142
2019-07-01 03:23:33
193.188.22.220 attack
2019-06-30T18:46:31.629451Z \[cowrie.ssh.factory.CowrieSSHFactory\] New connection: 193.188.22.220:12772 \(107.175.91.48:22\) \[session: ec30bbbca81b\]
2019-06-30T18:46:34.431995Z \[cowrie.ssh.factory.CowrieSSHFactory\] New connection: 193.188.22.220:15907 \(107.175.91.48:22\) \[session: 3149c6749f94\]
...
2019-07-01 03:06:40

Recently Reported IPs

212.6.213.148 22.151.16.149 107.137.232.79 207.64.19.249
225.26.215.97 63.230.206.245 6.117.191.179 95.178.79.199
147.20.209.191 174.25.119.100 23.249.152.112 86.29.71.149
173.209.118.201 41.141.27.62 227.186.234.201 69.207.241.63
91.172.173.129 37.177.74.22 228.72.118.129 77.106.33.64