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: Ban Yang Sam Ton

Region: Phetchabun

Country: Thailand

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

;; QUESTION SECTION:
;1.0.245.99.			IN	A

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

;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 24 08:20:39 CST 2022
;; MSG SIZE  rcvd: 103
Host info
99.245.0.1.in-addr.arpa domain name pointer node-n6r.pool-1-0.dynamic.totinternet.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
99.245.0.1.in-addr.arpa	name = node-n6r.pool-1-0.dynamic.totinternet.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
139.59.59.187 attack
Nov 16 19:52:33 gw1 sshd[31357]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.59.187
Nov 16 19:52:35 gw1 sshd[31357]: Failed password for invalid user informix from 139.59.59.187 port 52434 ssh2
...
2019-11-17 00:25:10
134.209.175.214 attack
fire
2019-11-17 00:52:11
109.244.96.201 attackbots
2019-11-16T16:30:46.893325abusebot-5.cloudsearch.cf sshd\[30267\]: Invalid user amha from 109.244.96.201 port 35968
2019-11-17 01:03:27
192.144.184.199 attack
Automatic report - Banned IP Access
2019-11-17 00:20:26
94.23.41.222 attackspam
Nov 16 17:40:48 server sshd\[15053\]: Invalid user dck from 94.23.41.222
Nov 16 17:40:48 server sshd\[15053\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ns323499.ip-94-23-41.eu 
Nov 16 17:40:50 server sshd\[15053\]: Failed password for invalid user dck from 94.23.41.222 port 33166 ssh2
Nov 16 17:54:38 server sshd\[18662\]: Invalid user iv from 94.23.41.222
Nov 16 17:54:38 server sshd\[18662\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ns323499.ip-94-23-41.eu 
...
2019-11-17 00:33:23
178.128.108.19 attackbots
Nov 16 06:41:30 php1 sshd\[5186\]: Invalid user wait from 178.128.108.19
Nov 16 06:41:30 php1 sshd\[5186\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.108.19
Nov 16 06:41:31 php1 sshd\[5186\]: Failed password for invalid user wait from 178.128.108.19 port 43700 ssh2
Nov 16 06:49:21 php1 sshd\[5845\]: Invalid user test from 178.128.108.19
Nov 16 06:49:21 php1 sshd\[5845\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.108.19
2019-11-17 01:01:52
103.10.52.150 attackspambots
23/tcp
[2019-11-16]1pkt
2019-11-17 00:58:58
118.25.25.207 attackbots
Nov 16 16:52:31 tux-35-217 sshd\[8521\]: Invalid user contents from 118.25.25.207 port 46962
Nov 16 16:52:31 tux-35-217 sshd\[8521\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.25.25.207
Nov 16 16:52:33 tux-35-217 sshd\[8521\]: Failed password for invalid user contents from 118.25.25.207 port 46962 ssh2
Nov 16 16:57:50 tux-35-217 sshd\[8548\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.25.25.207  user=root
...
2019-11-17 00:52:26
193.70.39.175 attack
Nov 16 15:52:18 mail sshd[9586]: Invalid user guest from 193.70.39.175
Nov 16 15:52:18 mail sshd[9586]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.70.39.175
Nov 16 15:52:18 mail sshd[9586]: Invalid user guest from 193.70.39.175
Nov 16 15:52:20 mail sshd[9586]: Failed password for invalid user guest from 193.70.39.175 port 37230 ssh2
...
2019-11-17 00:35:29
106.51.72.240 attack
SSH Brute Force
2019-11-17 01:08:56
212.107.248.56 attackbotsspam
1433/tcp
[2019-11-16]1pkt
2019-11-17 00:49:49
41.45.213.122 attackspambots
IP Ban Report :  
 https://help-dysk.pl/wordpress-firewall-plugins/ip/41.45.213.122/ 
 
 EG - 1H : (39)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : EG 
 NAME ASN : ASN8452 
 
 IP : 41.45.213.122 
 
 CIDR : 41.45.192.0/19 
 
 PREFIX COUNT : 833 
 
 UNIQUE IP COUNT : 7610368 
 
 
 ATTACKS DETECTED ASN8452 :  
  1H - 2 
  3H - 8 
  6H - 14 
 12H - 22 
 24H - 36 
 
 DateTime : 2019-11-16 15:52:24 
 
 INFO : Port Scan TELNET Detected and Blocked by ADMIN  - data recovery
2019-11-17 00:30:57
129.204.50.75 attackspambots
2019-11-16T16:39:27.676472shield sshd\[5945\]: Invalid user awkward from 129.204.50.75 port 51582
2019-11-16T16:39:27.680809shield sshd\[5945\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.50.75
2019-11-16T16:39:29.516241shield sshd\[5945\]: Failed password for invalid user awkward from 129.204.50.75 port 51582 ssh2
2019-11-16T16:44:44.989054shield sshd\[6940\]: Invalid user collete from 129.204.50.75 port 59098
2019-11-16T16:44:44.994147shield sshd\[6940\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.50.75
2019-11-17 00:59:37
128.199.46.189 attackbots
fire
2019-11-17 01:02:25
13.81.69.78 attackbots
fire
2019-11-17 00:57:59

Recently Reported IPs

1.0.245.84 1.0.246.100 1.0.246.122 1.0.246.13
1.0.246.138 1.0.246.142 1.0.246.149 1.0.246.152
1.0.246.17 1.0.246.176 1.0.246.18 1.0.246.187
1.0.246.191 1.0.246.196 1.0.246.2 1.0.246.212
1.0.246.215 1.0.246.220 1.0.246.228 1.0.246.236