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: San Francisco

Region: California

Country: United States

Internet Service Provider: DigitalOcean LLC

Hostname: unknown

Organization: unknown

Usage Type: Data Center/Web Hosting/Transit

Comments:
Type Details Datetime
attack
Apr 28 07:00:37 askasleikir sshd[20315]: Connection closed by 162.243.134.31 port 41312 [preauth]
2020-04-28 20:46:56
attackbots
Unauthorized connection attempt detected from IP address 162.243.134.31 to port 22
2020-04-14 17:40:01
attackbotsspam
Lines containing failures of 162.243.134.31
Mar 16 16:07:44 UTC__SANYALnet-Labs__cac12 postfix/smtps/smtpd[21303]: warning: hostname zg-0312c-466.stretchoid.com does not resolve to address 162.243.134.31
Mar 16 16:07:44 UTC__SANYALnet-Labs__cac12 postfix/smtps/smtpd[21303]: connect from unknown[162.243.134.31]
Mar 16 16:07:54 UTC__SANYALnet-Labs__cac12 postfix/smtps/smtpd[21303]: lost connection after CONNECT from unknown[162.243.134.31]
Mar 16 16:07:54 UTC__SANYALnet-Labs__cac12 postfix/smtps/smtpd[21303]: disconnect from unknown[162.243.134.31]


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=162.243.134.31
2020-03-17 06:50:11
Comments on same subnet:
IP Type Details Datetime
162.243.134.57 attack
Malicious IP
2024-04-30 13:38:55
162.243.134.4 attackspam
scans once in preceeding hours on the ports (in chronological order) 5800 resulting in total of 50 scans from 162.243.0.0/16 block.
2020-04-25 23:28:29
162.243.134.59 attackspambots
scans once in preceeding hours on the ports (in chronological order) 2049 resulting in total of 50 scans from 162.243.0.0/16 block.
2020-04-25 23:28:12
162.243.134.25 attackbots
Port scan(s) denied
2020-04-22 17:32:16
162.243.134.59 attack
20/4/18@16:43:59: FAIL: Alarm-SSH address from=162.243.134.59
...
2020-04-19 06:11:22
162.243.134.17 attackbotsspam
Port Scan: Events[1] countPorts[1]: 7210 ..
2020-04-15 21:43:05
162.243.134.25 attackspambots
Unauthorized connection attempt detected from IP address 162.243.134.25 to port 7574
2020-04-15 01:13:56
162.243.134.36 attackspambots
firewall-block, port(s): 1583/tcp
2020-04-09 00:39:08
162.243.134.30 attackbots
firewall-block, port(s): 65197/tcp
2020-04-06 09:26:48
162.243.134.56 attackbotsspam
9160/tcp 3001/tcp 6379/tcp...
[2020-03-14/04-04]28pkt,25pt.(tcp),1pt.(udp)
2020-04-06 04:10:33
162.243.134.15 attackspam
Unauthorized connection attempt detected from IP address 162.243.134.15 to port 5007
2020-04-06 04:04:33
162.243.134.15 attackbotsspam
[SMTP/25/465/587 Probe]
TLS/SSL handshake failed:[ wrong version number]

*(03281322)
2020-03-28 18:32:08
162.243.134.30 attack
firewall-block, port(s): 8889/tcp
2020-03-27 16:07:35
162.243.134.4 attack
22/tcp 2404/tcp 8888/tcp...
[2020-03-13/26]11pkt,10pt.(tcp)
2020-03-26 16:06:13
162.243.134.59 attackspambots
25266/tcp 2083/tcp 18892/tcp...
[2020-02-15/03-25]26pkt,23pt.(tcp),2pt.(udp)
2020-03-25 19:40:29
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 162.243.134.31
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 32381
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

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

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

;; Query time: 106 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Mar 17 06:50:07 CST 2020
;; MSG SIZE  rcvd: 118
Host info
31.134.243.162.in-addr.arpa domain name pointer zg-0312c-466.stretchoid.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
31.134.243.162.in-addr.arpa	name = zg-0312c-466.stretchoid.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
186.200.205.218 attackspambots
Unauthorized connection attempt from IP address 186.200.205.218 on Port 445(SMB)
2019-12-06 09:26:41
36.91.152.234 attack
Dec  6 01:14:11 *** sshd[19407]: Invalid user summerlin from 36.91.152.234
2019-12-06 09:21:13
123.148.208.189 attackspam
Scanning unused Default website or suspicious access to valid sites from IP marked as abusive
2019-12-06 09:53:31
220.181.108.185 attackbotsspam
Automatic report - Banned IP Access
2019-12-06 09:31:10
62.234.154.64 attack
Dec  6 02:38:21 localhost sshd\[12544\]: Invalid user miro from 62.234.154.64
Dec  6 02:38:21 localhost sshd\[12544\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.234.154.64
Dec  6 02:38:23 localhost sshd\[12544\]: Failed password for invalid user miro from 62.234.154.64 port 33976 ssh2
Dec  6 02:44:26 localhost sshd\[12842\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.234.154.64  user=www-data
Dec  6 02:44:28 localhost sshd\[12842\]: Failed password for www-data from 62.234.154.64 port 33456 ssh2
...
2019-12-06 09:47:31
91.242.213.8 attackspambots
2019-12-06T01:37:04.972950abusebot-5.cloudsearch.cf sshd\[19958\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ns1.navigator-com.ru  user=root
2019-12-06 09:41:14
208.91.198.76 attack
WordPress brute force
2019-12-06 09:49:30
222.180.162.8 attackspam
Dec  6 06:57:11 vibhu-HP-Z238-Microtower-Workstation sshd\[23562\]: Invalid user gggg from 222.180.162.8
Dec  6 06:57:11 vibhu-HP-Z238-Microtower-Workstation sshd\[23562\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.180.162.8
Dec  6 06:57:12 vibhu-HP-Z238-Microtower-Workstation sshd\[23562\]: Failed password for invalid user gggg from 222.180.162.8 port 37748 ssh2
Dec  6 07:05:33 vibhu-HP-Z238-Microtower-Workstation sshd\[24062\]: Invalid user 123456 from 222.180.162.8
Dec  6 07:05:33 vibhu-HP-Z238-Microtower-Workstation sshd\[24062\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.180.162.8
...
2019-12-06 09:41:36
124.156.218.111 attackspam
firewall-block, port(s): 8060/tcp
2019-12-06 09:40:49
189.240.58.174 attackspam
Unauthorized connection attempt from IP address 189.240.58.174 on Port 445(SMB)
2019-12-06 09:42:11
190.39.255.129 attackbotsspam
Unauthorized connection attempt from IP address 190.39.255.129 on Port 445(SMB)
2019-12-06 09:17:06
106.13.118.162 attackspambots
Dec  5 20:06:49 ny01 sshd[10930]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.118.162
Dec  5 20:06:51 ny01 sshd[10930]: Failed password for invalid user hirayama from 106.13.118.162 port 35574 ssh2
Dec  5 20:13:53 ny01 sshd[11606]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.118.162
2019-12-06 09:34:02
177.73.248.35 attackbots
Dec  5 15:13:41 auw2 sshd\[6517\]: Invalid user sarah from 177.73.248.35
Dec  5 15:13:41 auw2 sshd\[6517\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.73.248.35
Dec  5 15:13:43 auw2 sshd\[6517\]: Failed password for invalid user sarah from 177.73.248.35 port 42422 ssh2
Dec  5 15:21:28 auw2 sshd\[7217\]: Invalid user arma3 from 177.73.248.35
Dec  5 15:21:28 auw2 sshd\[7217\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.73.248.35
2019-12-06 09:33:18
92.118.160.29 attack
firewall-block, port(s): 5909/tcp
2019-12-06 09:15:56
49.235.188.239 attack
49.235.188.239 - - [05/Dec/2019:19:32:56 +0500] "GET /index.php HTTP/1.1" 301 185 "http://194.67.210.115:80/index.php" "Mozilla/4.0 (compatible; MSIE 9.0; Windows NT 6.1)"
2019-12-06 09:46:20

Recently Reported IPs

85.236.189.175 137.122.25.137 77.222.113.32 72.42.164.144
96.127.7.154 187.36.222.179 112.133.251.213 184.10.39.217
93.119.232.188 88.181.209.109 180.247.65.113 175.8.61.119
171.245.98.7 187.61.124.48 87.236.212.167 82.165.103.45
112.206.170.166 94.181.27.248 201.103.225.3 142.93.176.17