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

;; QUESTION SECTION:
;105.213.95.4.			IN	A

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

;; Query time: 68 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 25 20:56:08 CST 2022
;; MSG SIZE  rcvd: 105
Host info
4.95.213.105.in-addr.arpa domain name pointer 105-213-95-4.access.mtnbusiness.co.za.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
4.95.213.105.in-addr.arpa	name = 105-213-95-4.access.mtnbusiness.co.za.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
103.90.205.55 attackbotsspam
Unauthorized connection attempt detected from IP address 103.90.205.55 to port 8080 [J]
2020-01-05 03:01:34
207.236.200.70 attack
Jan  4 20:06:11 nextcloud sshd\[6147\]: Invalid user cloud from 207.236.200.70
Jan  4 20:06:11 nextcloud sshd\[6147\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=207.236.200.70
Jan  4 20:06:13 nextcloud sshd\[6147\]: Failed password for invalid user cloud from 207.236.200.70 port 38174 ssh2
...
2020-01-05 03:06:59
178.217.168.84 attackbots
Unauthorized connection attempt detected from IP address 178.217.168.84 to port 1433 [J]
2020-01-05 03:09:51
2.191.187.162 attackbots
Unauthorized connection attempt detected from IP address 2.191.187.162 to port 8080 [J]
2020-01-05 03:21:55
177.55.188.207 attackbots
Unauthorized connection attempt detected from IP address 177.55.188.207 to port 23 [J]
2020-01-05 02:56:16
200.41.116.42 attackbots
Unauthorized connection attempt detected from IP address 200.41.116.42 to port 80 [J]
2020-01-05 02:53:40
197.155.40.115 attackbots
Unauthorized connection attempt detected from IP address 197.155.40.115 to port 1433 [J]
2020-01-05 03:24:07
203.160.91.226 attackspam
Unauthorized connection attempt detected from IP address 203.160.91.226 to port 2220 [J]
2020-01-05 03:23:08
172.248.46.36 attack
Unauthorized connection attempt detected from IP address 172.248.46.36 to port 80 [J]
2020-01-05 02:56:56
222.72.137.108 attack
Unauthorized connection attempt detected from IP address 222.72.137.108 to port 2220 [J]
2020-01-05 02:53:15
221.220.23.204 attackbotsspam
Unauthorized connection attempt detected from IP address 221.220.23.204 to port 1433 [J]
2020-01-05 03:05:45
2.144.247.24 attackspam
Unauthorized connection attempt detected from IP address 2.144.247.24 to port 2220 [J]
2020-01-05 03:22:10
176.20.18.14 attackspambots
Unauthorized connection attempt detected from IP address 176.20.18.14 to port 9000 [J]
2020-01-05 03:10:20
186.193.198.240 attackbotsspam
Unauthorized connection attempt detected from IP address 186.193.198.240 to port 80 [J]
2020-01-05 03:08:59
46.242.10.165 attackspambots
Unauthorized connection attempt detected from IP address 46.242.10.165 to port 445 [J]
2020-01-05 03:19:25

Recently Reported IPs

105.213.95.189 105.213.95.224 105.213.95.228 101.132.40.220
105.213.95.203 105.213.95.248 105.213.95.25 105.213.95.252
105.213.95.27 105.213.95.59 105.213.95.40 105.213.95.75
101.132.40.250 105.213.95.78 105.213.95.89 105.213.96.101
105.213.95.6 105.213.95.86 105.213.96.119 105.213.96.13