103.145.13.48 - IPInfo

Basic Info

City: unknown

Region: unknown

Country: Netherlands

Internet Service Provider: unknown

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:

Make a comment on this IP

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:

Dig info:

; <<>> DiG 9.10.3-P4-Ubuntu <<>> 103.145.13.48
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 41091
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;103.145.13.48.			IN	A

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

;; Query time: 23 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Nov 14 06:14:15 CST 2023
;; MSG SIZE  rcvd: 106

Host info

Host 48.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 48.13.145.103.in-addr.arpa: NXDOMAIN

Related IP info:

Related comments:

IP	Type	Details	Datetime
111.229.63.21	attackspambots	Invalid user vanzandt from 111.229.63.21 port 34062	2020-05-28 14:44:16
209.141.41.4	attackspam	TCP (SYN) 209.141.41.4:38319 -> port 22, len 40	2020-05-28 14:48:33
45.9.148.131	attack	SSH login attempts.	2020-05-28 14:52:20
58.71.15.10	attack	Invalid user webcam from 58.71.15.10 port 33841	2020-05-28 14:55:19
35.241.123.113	attackspam	ssh brute force	2020-05-28 14:29:02
202.78.200.208	attackspam	SSH login attempts.	2020-05-28 15:02:26
218.92.0.191	attackspambots	05/28/2020-02:33:54.511249 218.92.0.191 Protocol: 6 ET SCAN Potential SSH Scan	2020-05-28 14:36:19
49.233.162.198	attackspambots	May 28 06:55:59 ns382633 sshd\[5917\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.233.162.198 user=root May 28 06:56:01 ns382633 sshd\[5917\]: Failed password for root from 49.233.162.198 port 49534 ssh2 May 28 07:18:26 ns382633 sshd\[9937\]: Invalid user guest02 from 49.233.162.198 port 33256 May 28 07:18:26 ns382633 sshd\[9937\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.233.162.198 May 28 07:18:28 ns382633 sshd\[9937\]: Failed password for invalid user guest02 from 49.233.162.198 port 33256 ssh2	2020-05-28 14:53:30
36.237.208.202	attackbots	Telnetd brute force attack detected by fail2ban	2020-05-28 14:34:08
104.248.137.95	attackbots	May 27 21:49:11 server1 sshd\[10705\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.137.95 user=root May 27 21:49:13 server1 sshd\[10705\]: Failed password for root from 104.248.137.95 port 37270 ssh2 May 27 21:52:32 server1 sshd\[11722\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.137.95 user=root May 27 21:52:34 server1 sshd\[11722\]: Failed password for root from 104.248.137.95 port 42406 ssh2 May 27 21:55:57 server1 sshd\[12709\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.137.95 user=root ...	2020-05-28 14:57:15
120.211.61.239	attackbots	$f2bV_matches	2020-05-28 15:00:25
83.240.242.218	attackspam	SSH login attempts.	2020-05-28 14:26:59
139.59.66.101	attackspambots	SSH login attempts.	2020-05-28 14:44:37
195.70.59.121	attackspambots	2020-05-28T06:20:07.401271shield sshd\[7479\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=195.70.59.121 user=root 2020-05-28T06:20:09.228852shield sshd\[7479\]: Failed password for root from 195.70.59.121 port 33318 ssh2 2020-05-28T06:23:54.322582shield sshd\[8316\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=195.70.59.121 user=root 2020-05-28T06:23:56.316194shield sshd\[8316\]: Failed password for root from 195.70.59.121 port 46354 ssh2 2020-05-28T06:27:43.723730shield sshd\[9229\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=195.70.59.121 user=root	2020-05-28 14:37:55
211.38.132.36	attack	$f2bV_matches	2020-05-28 14:50:49

Recently Reported IPs

85.209.11.226	40.184.186.32	119.3.93.66	124.71.93.234
57.134.161.139	98.98.203.179	215.112.200.106	10.117.181.233
154.80.88.214	154.80.88.69	154.80.88.5	154.80.88.21
154.80.88.161	154.80.88.57	154.80.88.15	116.30.7.219
125.227.54.151	125.227.54.152	34.141.180.61	14.116.174.219