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: Columbus

Region: Ohio

Country: United States

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 <<>> 52.94.22.0
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 13901
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;52.94.22.0.			IN	A

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

;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Jan 21 08:02:06 CST 2022
;; MSG SIZE  rcvd: 103
Host info
0.22.94.52.in-addr.arpa domain name pointer dynamodb.us-gov-east-1.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
0.22.94.52.in-addr.arpa	name = dynamodb.us-gov-east-1.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
189.89.218.29 attack
Jun 29 23:40:38 web1 postfix/smtpd[3898]: warning: 189-089-218-029.static.stratus.com.br[189.89.218.29]: SASL PLAIN authentication failed: authentication failure
...
2019-06-30 16:06:48
96.57.28.210 attackspam
Jun 30 09:17:04 mail sshd[11504]: Invalid user st from 96.57.28.210
Jun 30 09:17:04 mail sshd[11504]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=96.57.28.210
Jun 30 09:17:04 mail sshd[11504]: Invalid user st from 96.57.28.210
Jun 30 09:17:06 mail sshd[11504]: Failed password for invalid user st from 96.57.28.210 port 54709 ssh2
Jun 30 09:31:04 mail sshd[13311]: Invalid user admin from 96.57.28.210
...
2019-06-30 16:24:31
102.250.4.76 attackspam
Hit on /xmlrpc.php
2019-06-30 15:50:49
42.239.191.231 attackbots
Unauthorised access (Jun 30) SRC=42.239.191.231 LEN=40 TTL=50 ID=50675 TCP DPT=23 WINDOW=41167 SYN 
Unauthorised access (Jun 30) SRC=42.239.191.231 LEN=40 TTL=50 ID=29480 TCP DPT=23 WINDOW=3955 SYN
2019-06-30 15:59:03
14.238.12.90 attackbotsspam
445/tcp
[2019-06-30]1pkt
2019-06-30 15:54:09
177.66.235.48 attackspam
libpam_shield report: forced login attempt
2019-06-30 15:54:41
211.159.152.252 attack
Jun 30 07:30:35 hosting sshd[5612]: Invalid user testing from 211.159.152.252 port 44221
...
2019-06-30 15:53:08
62.234.139.150 attack
Jun 30 06:46:03 lnxweb61 sshd[19717]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.234.139.150
Jun 30 06:46:03 lnxweb61 sshd[19717]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.234.139.150
2019-06-30 16:16:42
61.72.254.71 attackspambots
Jun 30 08:03:47 work-partkepr sshd\[20599\]: Invalid user ftp from 61.72.254.71 port 43144
Jun 30 08:03:47 work-partkepr sshd\[20599\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.72.254.71
...
2019-06-30 16:10:54
206.189.118.156 attack
Triggered by Fail2Ban at Vostok web server
2019-06-30 16:43:04
116.52.44.109 attackbots
23/tcp
[2019-06-30]1pkt
2019-06-30 16:05:23
124.156.185.27 attack
445/tcp 2433/tcp 1433/tcp...
[2019-06-30]4pkt,4pt.(tcp)
2019-06-30 16:32:15
191.53.194.61 attackspambots
libpam_shield report: forced login attempt
2019-06-30 16:09:47
159.65.245.203 attackspambots
$f2bV_matches
2019-06-30 16:38:03
110.45.145.178 attack
$f2bV_matches
2019-06-30 16:32:42

Recently Reported IPs

206.10.54.102 215.175.145.130 52.58.28.0 250.119.96.163
3.2.10.51 79.117.81.241 3.218.5.3 229.50.76.123
46.4.0.0 7.86.116.254 82.28.108.135 1.81.28.1
200.17.1.1 2.56.8.11 209.171.112.102 0.1.4.151
117.111.178.70 225.228.192.131 1.0.2.221 125.126.193.156