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: Netherlands (the)

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
103.145.13.88 attack
Port Scan
2022-08-18 13:44:23
103.145.13.10 attack
TCP ports : 443
2020-11-06 18:32:07
103.145.13.149 attack
Severity: Medium
TypeMisc: Attack
Category: Dshield
Source: 103.145.13.149 : 42748
2020-10-21 16:53:33
103.145.13.124 attackspambots
ET DROP Dshield Block Listed Source group 1 - port: 5060 proto: sip cat: Misc Attackbytes: 452
2020-10-14 05:18:15
103.145.13.229 attackbots
ET DROP Dshield Block Listed Source group 1 - port: 5060 proto: sip cat: Misc Attackbytes: 461
2020-10-14 04:59:54
103.145.13.58 attackspam
ET DROP Dshield Block Listed Source group 1 - port: 5038 proto: tcp cat: Misc Attackbytes: 60
2020-10-13 20:33:43
103.145.13.58 attackspam
ET DROP Dshield Block Listed Source group 1 - port: 5038 proto: tcp cat: Misc Attackbytes: 60
2020-10-13 12:05:57
103.145.13.58 attack
ET CINS Active Threat Intelligence Poor Reputation IP group 95 - port: 5038 proto: tcp cat: Misc Attackbytes: 60
2020-10-13 04:55:55
103.145.13.229 attackspam
103.145.13.229 was recorded 6 times by 4 hosts attempting to connect to the following ports: 5060. Incident counter (4h, 24h, all-time): 6, 33, 646
2020-10-13 00:41:48
103.145.13.229 attackspambots
ET SCAN Sipvicious Scan - port: 5060 proto: sip cat: Attempted Information Leakbytes: 462
2020-10-12 16:06:39
103.145.13.193 attackbotsspam
Trying ports that it shouldn't be.
2020-10-10 05:42:03
103.145.13.193 attackbotsspam
 UDP 103.145.13.193:5140 -> port 5060, len 417
2020-10-09 21:47:36
103.145.13.193 attack
Port scan denied
2020-10-09 13:37:25
103.145.13.124 attackbotsspam
UDP port : 5060
2020-10-09 04:44:22
103.145.13.124 attackbots
UDP port : 5060
2020-10-08 20:54:40
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 103.145.13.243
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 8494
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;103.145.13.243.			IN	A

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

;; Query time: 15 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Dec 10 22:06:01 CST 2024
;; MSG SIZE  rcvd: 107
Host info
Host 243.13.145.103.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 243.13.145.103.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
222.186.175.217 attackbotsspam
Oct 26 10:12:33 firewall sshd[6035]: Failed password for root from 222.186.175.217 port 28276 ssh2
Oct 26 10:12:50 firewall sshd[6035]: error: maximum authentication attempts exceeded for root from 222.186.175.217 port 28276 ssh2 [preauth]
Oct 26 10:12:50 firewall sshd[6035]: Disconnecting: Too many authentication failures [preauth]
...
2019-10-26 21:34:53
54.37.158.218 attack
Oct 26 03:22:50 kapalua sshd\[3348\]: Invalid user vagrant from 54.37.158.218
Oct 26 03:22:50 kapalua sshd\[3348\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.ip-54-37-158.eu
Oct 26 03:22:51 kapalua sshd\[3348\]: Failed password for invalid user vagrant from 54.37.158.218 port 42061 ssh2
Oct 26 03:27:00 kapalua sshd\[3696\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.ip-54-37-158.eu  user=root
Oct 26 03:27:02 kapalua sshd\[3696\]: Failed password for root from 54.37.158.218 port 33371 ssh2
2019-10-26 21:36:33
222.186.180.223 attackbotsspam
Oct 26 15:12:47 MK-Soft-Root2 sshd[8047]: Failed password for root from 222.186.180.223 port 6802 ssh2
Oct 26 15:12:54 MK-Soft-Root2 sshd[8047]: Failed password for root from 222.186.180.223 port 6802 ssh2
...
2019-10-26 21:17:37
124.89.8.196 attackspambots
Oct2614:36:16server6pure-ftpd:\(\?@124.89.8.196\)[WARNING]Authenticationfailedforuser[boltonholding]Oct2614:36:16server6pure-ftpd:\(\?@124.89.8.196\)[WARNING]Authenticationfailedforuser[anonymous]Oct2614:36:24server6pure-ftpd:\(\?@124.89.8.196\)[WARNING]Authenticationfailedforuser[boltonholding]Oct2614:36:24server6pure-ftpd:\(\?@124.89.8.196\)[WARNING]Authenticationfailedforuser[boltonholding]Oct2614:36:31server6pure-ftpd:\(\?@124.89.8.196\)[WARNING]Authenticationfailedforuser[boltonholding]Oct2614:36:37server6pure-ftpd:\(\?@124.89.8.196\)[WARNING]Authenticationfailedforuser[boltonholding]Oct2614:36:43server6pure-ftpd:\(\?@124.89.8.196\)[WARNING]Authenticationfailedforuser[boltonholding]Oct2614:36:50server6pure-ftpd:\(\?@124.89.8.196\)[WARNING]Authenticationfailedforuser[boltonholding]Oct2614:36:57server6pure-ftpd:\(\?@124.89.8.196\)[WARNING]Authenticationfailedforuser[boltonholding]Oct2614:37:04server6pure-ftpd:\(\?@124.89.8.196\)[WARNING]Authenticationfailedforuser[boltonholding]
2019-10-26 21:37:41
94.131.241.63 attack
Oct 26 09:37:17 web1 postfix/smtpd[32661]: warning: unknown[94.131.241.63]: SASL LOGIN authentication failed: authentication failure
...
2019-10-26 21:53:00
190.145.7.42 attackspambots
Oct 26 14:54:53 server sshd\[1595\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.145.7.42  user=root
Oct 26 14:54:55 server sshd\[1595\]: Failed password for root from 190.145.7.42 port 40160 ssh2
Oct 26 14:59:17 server sshd\[2898\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.145.7.42  user=root
Oct 26 14:59:19 server sshd\[2898\]: Failed password for root from 190.145.7.42 port 60838 ssh2
Oct 26 15:03:26 server sshd\[4615\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.145.7.42  user=root
...
2019-10-26 21:47:56
45.80.65.35 attackbots
2019-10-26T14:04:04.9548561240 sshd\[17988\]: Invalid user austin from 45.80.65.35 port 60534
2019-10-26T14:04:04.9574931240 sshd\[17988\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.80.65.35
2019-10-26T14:04:06.6209301240 sshd\[17988\]: Failed password for invalid user austin from 45.80.65.35 port 60534 ssh2
...
2019-10-26 21:20:51
91.103.31.45 attackbots
SPAM Delivery Attempt
2019-10-26 21:32:23
165.22.246.63 attack
Oct 26 15:07:47 MK-Soft-VM4 sshd[19587]: Failed password for root from 165.22.246.63 port 55778 ssh2
...
2019-10-26 21:44:37
149.28.116.58 attackbots
Automatic report - XMLRPC Attack
2019-10-26 21:50:06
222.186.175.140 attack
Oct 26 15:03:46 MK-Soft-Root2 sshd[6472]: Failed password for root from 222.186.175.140 port 4132 ssh2
Oct 26 15:03:52 MK-Soft-Root2 sshd[6472]: Failed password for root from 222.186.175.140 port 4132 ssh2
...
2019-10-26 21:52:11
165.22.182.168 attack
$f2bV_matches
2019-10-26 21:27:21
159.203.201.10 attackspambots
10/26/2019-08:03:32.218399 159.203.201.10 Protocol: 6 ET DROP Dshield Block Listed Source group 1
2019-10-26 21:45:15
2607:f298:6:a077::2f:e930 attackspambots
WordPress wp-login brute force :: 2607:f298:6:a077::2f:e930 0.072 BYPASS [26/Oct/2019:23:03:32  1100] [censored_4] "POST /wp-login.php HTTP/1.1" 200 3989 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
2019-10-26 21:44:05
121.133.169.254 attackbotsspam
Automatic report - Banned IP Access
2019-10-26 21:24:05

Recently Reported IPs

50.53.92.138 100.243.136.117 45.211.9.157 160.37.97.157
50.148.174.109 225.234.139.112 93.195.23.45 231.170.76.238
4.226.4.73 185.129.34.227 243.234.33.207 92.235.71.122
51.130.156.163 129.91.100.118 169.142.241.13 195.67.241.232
29.202.119.95 187.128.124.171 136.160.8.32 54.180.37.17