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

Region: New South Wales

Country: Australia

Internet Service Provider: unknown

Hostname: unknown

Organization: OVH SAS

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

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

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

;; Query time: 1 msec
;; SERVER: 67.207.67.3#53(67.207.67.3)
;; WHEN: Tue Apr 09 21:57:29 +08 2019
;; MSG SIZE  rcvd: 118

Host info
149.158.99.139.in-addr.arpa domain name pointer 149.ip-139-99-158.eu.
Nslookup info:
Server:		67.207.67.3
Address:	67.207.67.3#53

Non-authoritative answer:
149.158.99.139.in-addr.arpa	name = 149.ip-139-99-158.eu.

Authoritative answers can be found from:

Related IP info:
Related comments:
IP Type Details Datetime
196.52.43.56 attackspambots
Unauthorized connection attempt detected from IP address 196.52.43.56 to port 5903
2019-12-29 08:54:29
140.143.236.227 attackspam
Dec 28 08:41:11 server sshd\[1733\]: Failed password for invalid user dejongh from 140.143.236.227 port 38048 ssh2
Dec 29 02:54:42 server sshd\[32164\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.236.227  user=mysql
Dec 29 02:54:44 server sshd\[32164\]: Failed password for mysql from 140.143.236.227 port 59164 ssh2
Dec 29 03:06:38 server sshd\[3861\]: Invalid user ident from 140.143.236.227
Dec 29 03:06:38 server sshd\[3861\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.236.227 
...
2019-12-29 09:00:58
196.52.43.58 attack
Unauthorized connection attempt detected from IP address 196.52.43.58 to port 5986
2019-12-29 08:53:58
49.51.9.206 attack
Unauthorized connection attempt detected from IP address 49.51.9.206 to port 3774
2019-12-29 08:46:45
88.227.83.7 attackbotsspam
Unauthorized connection attempt detected from IP address 88.227.83.7 to port 85
2019-12-29 08:41:46
189.130.86.212 attackspambots
Unauthorized connection attempt detected from IP address 189.130.86.212 to port 80
2019-12-29 08:56:47
200.125.25.130 attackbotsspam
Unauthorized connection attempt detected from IP address 200.125.25.130 to port 83
2019-12-29 08:29:07
190.13.132.91 attackspam
Unauthorized connection attempt detected from IP address 190.13.132.91 to port 445
2019-12-29 08:55:37
188.214.163.146 attack
Unauthorized connection attempt detected from IP address 188.214.163.146 to port 5555
2019-12-29 08:31:38
103.52.217.236 attackbotsspam
Unauthorized connection attempt detected from IP address 103.52.217.236 to port 6667
2019-12-29 08:39:00
78.186.128.245 attackspambots
Unauthorized connection attempt detected from IP address 78.186.128.245 to port 23
2019-12-29 08:43:37
190.175.30.86 attackbots
Unauthorized connection attempt detected from IP address 190.175.30.86 to port 2323
2019-12-29 08:30:59
131.0.248.199 attack
Unauthorized connection attempt detected from IP address 131.0.248.199 to port 80
2019-12-29 08:36:12
189.219.39.226 attackspam
Unauthorized connection attempt detected from IP address 189.219.39.226 to port 80
2019-12-29 08:55:56
203.251.29.206 attackspam
Unauthorized connection attempt detected from IP address 203.251.29.206 to port 4567
2019-12-29 08:27:39

Recently Reported IPs

177.124.173.19 105.141.131.121 94.198.160.56 69.150.96.144
181.118.101.217 200.239.128.60 202.130.122.50 195.96.230.200
90.107.233.96 195.245.230.2 87.117.60.100 198.37.147.111
121.28.95.69 59.92.3.113 170.233.117.57 198.57.168.53
187.32.11.45 208.73.56.114 14.235.215.72 150.95.25.106