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

Region: unknown

Country: South Africa

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

;; QUESTION SECTION:
;105.247.134.140.		IN	A

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

;; Query time: 19 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 25 21:07:09 CST 2022
;; MSG SIZE  rcvd: 108
Host info
140.134.247.105.in-addr.arpa domain name pointer vc-vb-105-247-134-140.lte.vodacom.co.za.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
140.134.247.105.in-addr.arpa	name = vc-vb-105-247-134-140.lte.vodacom.co.za.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
81.170.246.37 attackspam
23/tcp 23/tcp
[2020-02-09]2pkt
2020-02-10 00:08:34
79.77.17.135 attackspam
Automatic report - Port Scan Attack
2020-02-10 00:08:15
185.200.118.49 attack
Feb  9 14:45:25 debian-2gb-nbg1-2 kernel: \[3515162.630821\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=185.200.118.49 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=244 ID=54321 PROTO=TCP SPT=43784 DPT=1723 WINDOW=65535 RES=0x00 SYN URGP=0
2020-02-10 00:27:12
77.26.64.57 attackbots
Telnet/23 MH Probe, BF, Hack -
2020-02-10 00:43:35
49.232.60.2 attack
Feb  9 00:27:13 server sshd\[1007\]: Invalid user bdn from 49.232.60.2
Feb  9 00:27:13 server sshd\[1007\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.232.60.2 
Feb  9 00:27:15 server sshd\[1007\]: Failed password for invalid user bdn from 49.232.60.2 port 56160 ssh2
Feb  9 16:35:11 server sshd\[24202\]: Invalid user us from 49.232.60.2
Feb  9 16:35:11 server sshd\[24202\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.232.60.2 
...
2020-02-10 00:40:09
49.232.4.101 attack
2020-02-09T10:03:51.6751841495-001 sshd[24438]: Invalid user hhf from 49.232.4.101 port 39888
2020-02-09T10:03:51.6783181495-001 sshd[24438]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.232.4.101
2020-02-09T10:03:51.6751841495-001 sshd[24438]: Invalid user hhf from 49.232.4.101 port 39888
2020-02-09T10:03:53.3523781495-001 sshd[24438]: Failed password for invalid user hhf from 49.232.4.101 port 39888 ssh2
2020-02-09T10:07:45.7653741495-001 sshd[24632]: Invalid user vym from 49.232.4.101 port 34116
2020-02-09T10:07:45.7687071495-001 sshd[24632]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.232.4.101
2020-02-09T10:07:45.7653741495-001 sshd[24632]: Invalid user vym from 49.232.4.101 port 34116
2020-02-09T10:07:47.8986331495-001 sshd[24632]: Failed password for invalid user vym from 49.232.4.101 port 34116 ssh2
2020-02-09T10:11:56.4002081495-001 sshd[24876]: Invalid user dw from 49.232.4.101 port 5
...
2020-02-10 00:14:21
45.148.10.141 attackspam
Port scan detected on ports: 8089[TCP], 8089[TCP], 8089[TCP]
2020-02-10 00:18:07
148.72.232.107 attackspam
Port scan on 1 port(s): 2083
2020-02-10 00:53:14
77.246.102.140 attackbotsspam
Feb  9 16:53:53 mout sshd[8301]: Invalid user xim from 77.246.102.140 port 60980
2020-02-10 00:06:53
37.49.226.111 attackbots
firewall-block, port(s): 50802/tcp
2020-02-10 00:12:39
92.222.224.189 attackbots
Feb  9 06:20:02 web1 sshd\[15486\]: Invalid user ysp from 92.222.224.189
Feb  9 06:20:02 web1 sshd\[15486\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=92.222.224.189
Feb  9 06:20:04 web1 sshd\[15486\]: Failed password for invalid user ysp from 92.222.224.189 port 35348 ssh2
Feb  9 06:22:32 web1 sshd\[15674\]: Invalid user khi from 92.222.224.189
Feb  9 06:22:32 web1 sshd\[15674\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=92.222.224.189
2020-02-10 00:25:59
218.92.0.158 attack
Feb  9 17:15:51 * sshd[8882]: Failed password for root from 218.92.0.158 port 10053 ssh2
Feb  9 17:16:04 * sshd[8882]: error: maximum authentication attempts exceeded for root from 218.92.0.158 port 10053 ssh2 [preauth]
2020-02-10 00:19:46
93.174.95.106 attack
Feb  9 16:16:12 debian-2gb-nbg1-2 kernel: \[3520609.807334\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=93.174.95.106 DST=195.201.40.59 LEN=44 TOS=0x10 PREC=0x00 TTL=120 ID=45275 PROTO=TCP SPT=18438 DPT=2323 WINDOW=7589 RES=0x00 SYN URGP=0
2020-02-10 00:18:38
197.210.28.61 attackspambots
1581255323 - 02/09/2020 14:35:23 Host: 197.210.28.61/197.210.28.61 Port: 445 TCP Blocked
2020-02-10 00:24:49
49.235.246.127 attackbots
Feb  9 04:47:14 web9 sshd\[8924\]: Invalid user lbv from 49.235.246.127
Feb  9 04:47:14 web9 sshd\[8924\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.246.127
Feb  9 04:47:16 web9 sshd\[8924\]: Failed password for invalid user lbv from 49.235.246.127 port 38072 ssh2
Feb  9 04:48:38 web9 sshd\[9145\]: Invalid user lqk from 49.235.246.127
Feb  9 04:48:38 web9 sshd\[9145\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.246.127
2020-02-10 00:22:55

Recently Reported IPs

105.247.131.180 105.247.132.132 105.247.131.97 105.247.134.185
105.247.134.193 105.247.134.91 105.247.135.135 101.205.213.84
105.247.135.211 105.247.135.246 105.247.139.150 105.247.134.69
105.247.137.92 105.247.140.3 105.247.140.69 105.247.139.83
101.205.213.97 105.247.143.210 105.247.143.18 105.247.143.178