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

Region: Gauteng

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:
IP Type Details Datetime
102.130.118.83 attackbotsspam
Repeated RDP login failures. Last user: T1
2020-07-24 06:02:16
102.130.118.84 attack
Apr 17 19:07:56 php1 sshd\[11238\]: Invalid user od from 102.130.118.84
Apr 17 19:07:56 php1 sshd\[11238\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=102.130.118.84
Apr 17 19:07:58 php1 sshd\[11238\]: Failed password for invalid user od from 102.130.118.84 port 49872 ssh2
Apr 17 19:12:54 php1 sshd\[11779\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=102.130.118.84  user=root
Apr 17 19:12:56 php1 sshd\[11779\]: Failed password for root from 102.130.118.84 port 60402 ssh2
2020-04-18 13:32:17
102.130.118.156 attackbots
Mar  6 10:39:56 MK-Soft-Root1 sshd[2768]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=102.130.118.156 
Mar  6 10:39:57 MK-Soft-Root1 sshd[2768]: Failed password for invalid user 12345 from 102.130.118.156 port 57844 ssh2
...
2020-03-06 21:07:54
102.130.118.156 attack
Feb 28 19:49:43 server6 sshd[8716]: Failed password for invalid user master from 102.130.118.156 port 41488 ssh2
Feb 28 19:49:43 server6 sshd[8716]: Received disconnect from 102.130.118.156: 11: Bye Bye [preauth]
Feb 28 20:03:20 server6 sshd[22685]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=102.130.118.156  user=r.r
Feb 28 20:03:22 server6 sshd[22685]: Failed password for r.r from 102.130.118.156 port 46528 ssh2
Feb 28 20:03:22 server6 sshd[22685]: Received disconnect from 102.130.118.156: 11: Bye Bye [preauth]
Feb 28 20:10:28 server6 sshd[29546]: Failed password for invalid user qtss from 102.130.118.156 port 49560 ssh2
Feb 28 20:10:28 server6 sshd[29546]: Received disconnect from 102.130.118.156: 11: Bye Bye [preauth]
Feb 28 20:15:17 server6 sshd[1530]: Failed password for invalid user thomas from 102.130.118.156 port 38316 ssh2
Feb 28 20:15:17 server6 sshd[1530]: Received disconnect from 102.130.118.156: 11: Bye Bye [prea........
-------------------------------
2020-03-01 22:34:45
102.130.118.156 attackbots
Feb 29 01:31:41 plusreed sshd[17300]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=102.130.118.156  user=sshd
Feb 29 01:31:43 plusreed sshd[17300]: Failed password for sshd from 102.130.118.156 port 52888 ssh2
...
2020-02-29 15:08:02
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 102.130.118.71
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 28850
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;102.130.118.71.			IN	A

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

;; Query time: 18 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat May 21 16:39:01 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 71.118.130.102.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 71.118.130.102.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
218.155.242.149 attack
Unauthorized connection attempt detected from IP address 218.155.242.149 to port 8000 [J]
2020-01-06 18:16:48
178.151.210.92 attack
Unauthorized connection attempt detected from IP address 178.151.210.92 to port 80 [J]
2020-01-06 18:45:36
206.189.133.82 attackbots
Jan  6 08:45:39 icinga sshd[21573]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.133.82
Jan  6 08:45:41 icinga sshd[21573]: Failed password for invalid user bpz from 206.189.133.82 port 32346 ssh2
...
2020-01-06 18:40:03
115.79.103.134 attack
Unauthorized connection attempt detected from IP address 115.79.103.134 to port 88 [J]
2020-01-06 18:49:56
42.113.229.82 attackbotsspam
Unauthorized connection attempt detected from IP address 42.113.229.82 to port 23 [T]
2020-01-06 18:33:26
49.235.161.202 attackbotsspam
Unauthorized connection attempt detected from IP address 49.235.161.202 to port 2220 [J]
2020-01-06 18:32:27
124.156.50.52 attack
Unauthorized connection attempt detected from IP address 124.156.50.52 to port 6001 [J]
2020-01-06 18:48:35
184.20.9.242 attack
Unauthorized connection attempt detected from IP address 184.20.9.242 to port 8181 [J]
2020-01-06 18:20:12
193.254.135.252 attackspam
Unauthorized connection attempt detected from IP address 193.254.135.252 to port 2220 [J]
2020-01-06 18:19:39
74.82.47.3 attackbotsspam
Unauthorized connection attempt detected from IP address 74.82.47.3 to port 389
2020-01-06 18:29:40
223.149.206.93 attackbots
Unauthorized connection attempt detected from IP address 223.149.206.93 to port 23 [J]
2020-01-06 18:14:27
95.237.225.22 attackbots
Unauthorized connection attempt detected from IP address 95.237.225.22 to port 8081 [J]
2020-01-06 18:26:41
220.182.47.116 attack
Unauthorized connection attempt detected from IP address 220.182.47.116 to port 8088 [J]
2020-01-06 18:36:07
113.162.191.4 attackspam
Unauthorized connection attempt detected from IP address 113.162.191.4 to port 22 [J]
2020-01-06 18:50:14
219.79.177.251 attack
Unauthorized connection attempt detected from IP address 219.79.177.251 to port 5555 [J]
2020-01-06 18:16:27

Recently Reported IPs

102.130.118.226 102.130.118.96 102.130.77.201 102.130.79.1
102.130.79.254 102.131.20.12 102.132.9.2 102.133.133.95
102.133.237.39 102.134.0.10 102.134.158.174 102.134.158.234
102.134.159.26 102.134.167.154 102.134.167.59 102.134.168.200
102.134.168.77 102.134.169.137 102.134.169.95 102.134.181.251