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

Region: unknown

Country: Singapore

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

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

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

;; Query time: 535 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon May 18 07:55:29 CST 2020
;; MSG SIZE  rcvd: 115
Host info
2.58.139.18.in-addr.arpa domain name pointer ec2-18-139-58-2.ap-southeast-1.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
2.58.139.18.in-addr.arpa	name = ec2-18-139-58-2.ap-southeast-1.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
212.83.153.98 attackbots
SIP auth scanning - multiple failed SIP authentication
2020-01-09 22:03:23
178.92.188.183 attack
Telnet/23 MH Probe, BF, Hack -
2020-01-09 21:40:44
156.219.54.233 attack
20/1/9@08:10:47: FAIL: Alarm-Intrusion address from=156.219.54.233
...
2020-01-09 21:41:07
176.113.70.58 attackbotsspam
SIP/5060 Probe, BF, Hack -
2020-01-09 21:49:29
222.186.180.9 attack
Jan  9 14:38:06 localhost sshd\[3554\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.9  user=root
Jan  9 14:38:08 localhost sshd\[3554\]: Failed password for root from 222.186.180.9 port 9966 ssh2
Jan  9 14:38:11 localhost sshd\[3554\]: Failed password for root from 222.186.180.9 port 9966 ssh2
2020-01-09 21:39:11
80.66.81.143 attackbotsspam
Jan  9 14:27:43 srv01 postfix/smtpd\[3344\]: warning: unknown\[80.66.81.143\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jan  9 14:28:05 srv01 postfix/smtpd\[3346\]: warning: unknown\[80.66.81.143\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jan  9 14:29:00 srv01 postfix/smtpd\[3344\]: warning: unknown\[80.66.81.143\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jan  9 14:29:20 srv01 postfix/smtpd\[3346\]: warning: unknown\[80.66.81.143\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jan  9 14:32:13 srv01 postfix/smtpd\[3344\]: warning: unknown\[80.66.81.143\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-01-09 21:35:08
182.242.183.166 attackspam
Telnet/23 MH Probe, BF, Hack -
2020-01-09 22:05:22
46.38.144.179 attackspam
Jan  9 15:12:54 relay postfix/smtpd\[18168\]: warning: unknown\[46.38.144.179\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jan  9 15:13:09 relay postfix/smtpd\[15549\]: warning: unknown\[46.38.144.179\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jan  9 15:13:41 relay postfix/smtpd\[18167\]: warning: unknown\[46.38.144.179\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jan  9 15:13:57 relay postfix/smtpd\[15548\]: warning: unknown\[46.38.144.179\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jan  9 15:14:28 relay postfix/smtpd\[18167\]: warning: unknown\[46.38.144.179\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-01-09 22:17:36
222.186.30.187 attackbotsspam
Jan  9 14:54:40 debian64 sshd\[9167\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.30.187  user=root
Jan  9 14:54:41 debian64 sshd\[9167\]: Failed password for root from 222.186.30.187 port 33833 ssh2
Jan  9 14:54:43 debian64 sshd\[9167\]: Failed password for root from 222.186.30.187 port 33833 ssh2
...
2020-01-09 21:57:03
61.177.172.128 attackbots
Jan  9 15:11:27 tuxlinux sshd[47683]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.177.172.128  user=root
...
2020-01-09 22:13:37
222.186.180.6 attackbots
Jan  9 14:58:50 eventyay sshd[5885]: Failed password for root from 222.186.180.6 port 48950 ssh2
Jan  9 14:59:04 eventyay sshd[5885]: error: maximum authentication attempts exceeded for root from 222.186.180.6 port 48950 ssh2 [preauth]
Jan  9 14:59:11 eventyay sshd[5887]: Failed password for root from 222.186.180.6 port 16270 ssh2
...
2020-01-09 22:04:46
168.128.86.35 attackbotsspam
Jan  9 03:23:45 eddieflores sshd\[10613\]: Invalid user mvq from 168.128.86.35
Jan  9 03:23:45 eddieflores sshd\[10613\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.128.86.35
Jan  9 03:23:48 eddieflores sshd\[10613\]: Failed password for invalid user mvq from 168.128.86.35 port 59958 ssh2
Jan  9 03:27:04 eddieflores sshd\[10938\]: Invalid user sysop from 168.128.86.35
Jan  9 03:27:04 eddieflores sshd\[10938\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.128.86.35
2020-01-09 21:39:56
192.241.201.182 attack
Too many connections or unauthorized access detected from Arctic banned ip
2020-01-09 21:43:55
106.12.91.209 attackspambots
Jan  9 14:10:49 srv206 sshd[21328]: Invalid user fastuser from 106.12.91.209
Jan  9 14:10:49 srv206 sshd[21328]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.91.209
Jan  9 14:10:49 srv206 sshd[21328]: Invalid user fastuser from 106.12.91.209
Jan  9 14:10:51 srv206 sshd[21328]: Failed password for invalid user fastuser from 106.12.91.209 port 37868 ssh2
...
2020-01-09 21:37:42
87.134.19.213 attackspambots
detected by Fail2Ban
2020-01-09 22:19:47

Recently Reported IPs

15.236.175.94 152.160.3.255 12.72.103.168 209.50.123.94
87.22.252.205 190.47.60.203 221.228.175.247 64.21.86.99
222.5.125.130 49.47.202.192 171.36.33.192 208.2.55.211
1.220.33.254 70.167.123.196 46.204.110.78 75.74.38.224
71.175.249.5 87.142.230.188 155.207.16.50 82.136.117.206