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

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

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

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

;; Query time: 50 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Jan 11 05:38:02 CST 2020
;; MSG SIZE  rcvd: 118
Host info
Host 197.145.10.165.in-addr.arpa not found: 2(SERVFAIL)
Nslookup info:
;; Got SERVFAIL reply from 100.100.2.136, trying next server
;; Got SERVFAIL reply from 100.100.2.138, trying next server
Server:		100.100.2.138
Address:	100.100.2.138#53

** server can't find 197.145.10.165.in-addr.arpa: SERVFAIL

Related IP info:
Related comments:
IP Type Details Datetime
45.79.152.7 attackbots
*Port Scan* detected from 45.79.152.7 (US/United States/jscan001.ampereinnotech.com). 11 hits in the last 130 seconds
2019-11-10 13:13:46
110.34.1.157 attack
IP Ban Report :  
 https://help-dysk.pl/wordpress-firewall-plugins/ip/110.34.1.157/ 
 
 NP - 1H : (1)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : NP 
 NAME ASN : ASN4007 
 
 IP : 110.34.1.157 
 
 CIDR : 110.34.1.0/24 
 
 PREFIX COUNT : 91 
 
 UNIQUE IP COUNT : 25088 
 
 
 ATTACKS DETECTED ASN4007 :  
  1H - 1 
  3H - 1 
  6H - 1 
 12H - 1 
 24H - 1 
 
 DateTime : 2019-11-10 05:54:49 
 
 INFO : Port Scan TELNET Detected and Blocked by ADMIN  - data recovery
2019-11-10 13:15:05
83.97.20.235 attackspam
Caught in portsentry honeypot
2019-11-10 13:15:36
148.70.41.33 attack
2019-11-10T04:48:52.632411shield sshd\[16555\]: Invalid user 3 from 148.70.41.33 port 58382
2019-11-10T04:48:52.636334shield sshd\[16555\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.70.41.33
2019-11-10T04:48:54.806210shield sshd\[16555\]: Failed password for invalid user 3 from 148.70.41.33 port 58382 ssh2
2019-11-10T04:54:50.016606shield sshd\[17098\]: Invalid user fuckface from 148.70.41.33 port 39530
2019-11-10T04:54:50.021051shield sshd\[17098\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.70.41.33
2019-11-10 13:14:30
129.204.87.153 attackbots
Nov 10 01:54:12 firewall sshd[31455]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.87.153
Nov 10 01:54:12 firewall sshd[31455]: Invalid user lightdm from 129.204.87.153
Nov 10 01:54:14 firewall sshd[31455]: Failed password for invalid user lightdm from 129.204.87.153 port 40720 ssh2
...
2019-11-10 13:42:20
118.89.189.176 attackspam
SSH brutforce
2019-11-10 13:42:47
203.91.114.6 attack
Nov 10 06:16:35 dedicated sshd[30592]: Invalid user ina from 203.91.114.6 port 58932
2019-11-10 13:20:25
74.82.47.16 attackbots
873/tcp 445/tcp 5900/tcp...
[2019-09-15/11-09]31pkt,12pt.(tcp),1pt.(udp)
2019-11-10 13:37:59
216.10.245.5 attackbots
Nov  9 19:28:53 eddieflores sshd\[11681\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=216.10.245.5  user=root
Nov  9 19:28:55 eddieflores sshd\[11681\]: Failed password for root from 216.10.245.5 port 53870 ssh2
Nov  9 19:33:20 eddieflores sshd\[12214\]: Invalid user admin from 216.10.245.5
Nov  9 19:33:20 eddieflores sshd\[12214\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=216.10.245.5
Nov  9 19:33:22 eddieflores sshd\[12214\]: Failed password for invalid user admin from 216.10.245.5 port 35372 ssh2
2019-11-10 13:52:55
193.31.24.113 attackbotsspam
11/10/2019-06:25:58.917828 193.31.24.113 Protocol: 6 SURICATA SMTP tls rejected
2019-11-10 13:31:31
88.214.26.102 attackbots
11689/tcp 11789/tcp 60394/tcp...
[2019-09-15/11-10]165pkt,106pt.(tcp)
2019-11-10 13:55:10
122.165.140.147 attackspam
2019-11-10T06:09:55.605631scmdmz1 sshd\[26522\]: Invalid user lifei520 from 122.165.140.147 port 50824
2019-11-10T06:09:55.608420scmdmz1 sshd\[26522\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.165.140.147
2019-11-10T06:09:58.164754scmdmz1 sshd\[26522\]: Failed password for invalid user lifei520 from 122.165.140.147 port 50824 ssh2
...
2019-11-10 13:13:21
46.38.144.179 attackbotsspam
2019-11-10T06:15:30.149815mail01 postfix/smtpd[20960]: warning: unknown[46.38.144.179]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
2019-11-10T06:15:36.209806mail01 postfix/smtpd[26809]: warning: unknown[46.38.144.179]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
2019-11-10T06:15:53.357236mail01 postfix/smtpd[27964]: warning: unknown[46.38.144.179]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
2019-11-10 13:16:49
80.82.65.74 attackspambots
11/10/2019-00:44:41.407201 80.82.65.74 Protocol: 6 ET SCAN NMAP -sS window 1024
2019-11-10 13:55:39
121.204.166.240 attack
Nov 10 06:10:38 dedicated sshd[29592]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.204.166.240  user=root
Nov 10 06:10:40 dedicated sshd[29592]: Failed password for root from 121.204.166.240 port 49743 ssh2
2019-11-10 13:27:55

Recently Reported IPs

126.50.201.203 123.89.225.99 12.24.209.51 24.237.57.128
23.254.140.239 143.240.168.188 66.146.255.107 14.177.239.178
140.88.31.12 69.39.250.91 37.20.96.196 96.33.147.1
61.196.28.138 104.222.173.162 222.237.41.121 52.166.170.163
52.185.3.64 42.50.53.59 203.218.61.83 217.122.177.168