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

;; QUESTION SECTION:
;105.213.115.230.		IN	A

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

;; Query time: 126 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Apr 03 05:45:55 CST 2022
;; MSG SIZE  rcvd: 108
Host info
230.115.213.105.in-addr.arpa domain name pointer 105-213-115-230.access.mtnbusiness.co.za.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
230.115.213.105.in-addr.arpa	name = 105-213-115-230.access.mtnbusiness.co.za.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
159.89.194.103 attackbots
May 22 00:41:09 plex sshd[22447]: Invalid user uel from 159.89.194.103 port 35252
2020-05-22 06:43:24
170.250.108.37 attackbots
" "
2020-05-22 06:59:58
211.247.44.205 attackspam
20/5/21@16:26:42: FAIL: Alarm-Network address from=211.247.44.205
...
2020-05-22 06:33:17
134.122.21.209 attackspam
May 19 22:53:47 : SSH login attempts with invalid user
2020-05-22 06:46:59
77.247.108.119 attackspam
05/21/2020-16:26:33.312319 77.247.108.119 Protocol: 6 ET CINS Active Threat Intelligence Poor Reputation IP group 74
2020-05-22 06:42:34
222.128.15.208 attack
May 22 00:03:13 plex sshd[21367]: Invalid user pcq from 222.128.15.208 port 42690
2020-05-22 06:22:40
159.138.129.228 attackbots
05/21/2020-17:59:58.351622 159.138.129.228 Protocol: 6 ET SCAN Potential SSH Scan
2020-05-22 06:30:00
51.77.137.230 attackbots
Invalid user syz from 51.77.137.230 port 45578
2020-05-22 06:37:28
106.54.48.29 attackbotsspam
May 21 23:31:05 home sshd[12158]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.48.29
May 21 23:31:08 home sshd[12158]: Failed password for invalid user jbl from 106.54.48.29 port 34486 ssh2
May 21 23:35:05 home sshd[12777]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.48.29
...
2020-05-22 06:38:54
162.14.18.148 attack
SSH Invalid Login
2020-05-22 06:35:37
103.253.42.35 attackspambots
firewall-block, port(s): 80/tcp, 443/tcp
2020-05-22 06:32:27
185.49.240.20 attackspambots
May 22 00:16:20 plex sshd[21800]: Invalid user rum from 185.49.240.20 port 59416
2020-05-22 06:28:54
82.223.13.223 attackbots
May 21 23:58:03 server sshd[27772]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=82.223.13.223
May 21 23:58:05 server sshd[27772]: Failed password for invalid user kuc from 82.223.13.223 port 33288 ssh2
May 22 00:01:42 server sshd[30007]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=82.223.13.223
...
2020-05-22 06:24:46
51.77.211.94 attackspam
Invalid user bigdata from 51.77.211.94 port 54660
2020-05-22 06:47:19
222.186.42.137 attack
May 21 18:52:54 plusreed sshd[13260]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.42.137  user=root
May 21 18:52:56 plusreed sshd[13260]: Failed password for root from 222.186.42.137 port 25168 ssh2
...
2020-05-22 06:54:43

Recently Reported IPs

105.213.110.6 105.213.117.35 105.213.123.23 105.213.125.185
105.213.126.192 105.213.130.29 105.213.178.64 105.213.75.175
106.121.70.140 106.122.169.123 106.122.70.19 106.124.155.192
106.124.228.165 106.124.27.124 106.124.45.240 106.125.250.169
106.126.15.157 106.126.15.159 106.13.222.148 106.13.45.102