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

Region: Connecticut

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

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;3.245.20.22.			IN	A

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

;; Query time: 55 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Nov 03 13:53:56 CST 2019
;; MSG SIZE  rcvd: 115
Host info
Host 22.20.245.3.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 22.20.245.3.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
139.162.113.204 attack
[Mon Nov 11 21:37:51.254643 2019] [:error] [pid 715:tid 140006307493632] [client 139.162.113.204:59716] [client 139.162.113.204] ModSecurity: Access denied with code 403 (phase 2). Pattern match "^[\\\\d.:]+$" at REQUEST_HEADERS:Host. [file "/etc/modsecurity/owasp-modsecurity-crs-3.2.0/rules/REQUEST-920-PROTOCOL-ENFORCEMENT.conf"] [line "696"] [id "920350"] [msg "Host header is a numeric IP address"] [data "103.27.207.197"] [severity "WARNING"] [ver "OWASP_CRS/3.2.0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-protocol"] [tag "OWASP_CRS"] [tag "OWASP_CRS/PROTOCOL_VIOLATION/IP_HOST"] [tag "WASCTC/WASC-21"] [tag "OWASP_TOP_10/A7"] [tag "PCI/6.5.10"] [hostname "103.27.207.197"] [uri "/"] [unique_id "XclyP2H3g7BiAMdC0EfUKQAAAAA"]
...
2019-11-12 04:44:19
218.73.39.255 attackbots
Honeypot attack, port: 23, PTR: 255.39.73.218.broad.tz.zj.dynamic.163data.com.cn.
2019-11-12 04:45:01
218.92.0.157 attackspambots
$f2bV_matches
2019-11-12 04:39:37
82.238.107.124 attackspambots
Nov 11 21:05:01 MK-Soft-VM8 sshd[32552]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=82.238.107.124 
Nov 11 21:05:03 MK-Soft-VM8 sshd[32552]: Failed password for invalid user macaraeg from 82.238.107.124 port 40818 ssh2
...
2019-11-12 04:57:02
129.211.14.39 attackbotsspam
2019-11-11T19:52:46.835038hub.schaetter.us sshd\[3112\]: Invalid user symonds from 129.211.14.39 port 53128
2019-11-11T19:52:46.845967hub.schaetter.us sshd\[3112\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.211.14.39
2019-11-11T19:52:48.612827hub.schaetter.us sshd\[3112\]: Failed password for invalid user symonds from 129.211.14.39 port 53128 ssh2
2019-11-11T19:59:06.236448hub.schaetter.us sshd\[3144\]: Invalid user rf from 129.211.14.39 port 59520
2019-11-11T19:59:06.264224hub.schaetter.us sshd\[3144\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.211.14.39
...
2019-11-12 05:00:46
119.42.175.200 attack
Nov 11 21:20:29 serwer sshd\[29463\]: Invalid user libuuid from 119.42.175.200 port 49463
Nov 11 21:20:29 serwer sshd\[29463\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.42.175.200
Nov 11 21:20:30 serwer sshd\[29463\]: Failed password for invalid user libuuid from 119.42.175.200 port 49463 ssh2
...
2019-11-12 04:52:52
72.210.252.148 attack
IMAP
2019-11-12 04:44:45
50.73.116.41 attack
Masscan Port Scanning Tool Detection
2019-11-12 04:25:34
5.189.151.188 attackbots
5.189.151.188 was recorded 5 times by 2 hosts attempting to connect to the following ports: 80. Incident counter (4h, 24h, all-time): 5, 11, 27
2019-11-12 04:48:25
198.27.106.140 attackbotsspam
Automatic report - Port Scan
2019-11-12 04:36:12
77.247.110.42 attackspam
77.247.110.42 was recorded 5 times by 1 hosts attempting to connect to the following ports: 4000,4001,4002,4003,4004. Incident counter (4h, 24h, all-time): 5, 5, 30
2019-11-12 04:59:37
129.28.97.252 attack
Invalid user arleta from 129.28.97.252 port 59786
2019-11-12 04:32:36
222.82.237.238 attackbots
Nov 11 16:59:50 lnxmysql61 sshd[28055]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.82.237.238
2019-11-12 04:39:04
37.187.79.117 attackspam
Jun 27 15:15:46 vtv3 sshd\[4813\]: Invalid user prashant from 37.187.79.117 port 57645
Jun 27 15:15:46 vtv3 sshd\[4813\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.187.79.117
Jun 27 15:15:47 vtv3 sshd\[4813\]: Failed password for invalid user prashant from 37.187.79.117 port 57645 ssh2
Jun 27 15:17:47 vtv3 sshd\[5601\]: Invalid user support from 37.187.79.117 port 41371
Jun 27 15:17:47 vtv3 sshd\[5601\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.187.79.117
Jun 27 15:27:58 vtv3 sshd\[10417\]: Invalid user ts3 from 37.187.79.117 port 45466
Jun 27 15:27:58 vtv3 sshd\[10417\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.187.79.117
Jun 27 15:28:01 vtv3 sshd\[10417\]: Failed password for invalid user ts3 from 37.187.79.117 port 45466 ssh2
Jun 27 15:29:27 vtv3 sshd\[11023\]: Invalid user waski from 37.187.79.117 port 54117
Jun 27 15:29:27 vtv3 sshd\[11023\]: pam_un
2019-11-12 04:34:58
180.96.69.215 attackspam
2019-11-09 07:14:08 server sshd[37267]: Failed password for invalid user test from 180.96.69.215 port 40564 ssh2
2019-11-12 04:42:43

Recently Reported IPs

191.33.145.255 179.219.120.194 164.132.45.117 84.119.176.91
200.126.236.187 24.78.95.182 106.12.133.65 42.229.152.134
169.8.107.64 23.148.44.8 201.46.101.68 134.168.241.187
128.246.133.168 156.7.55.135 150.28.168.250 53.180.14.54
74.221.63.35 99.209.254.26 197.149.224.154 32.4.193.68