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

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

;; QUESTION SECTION:
;145.239.203.138.		IN	A

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

;; Query time: 37 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Feb 12 02:03:29 CST 2025
;; MSG SIZE  rcvd: 108
Host info
138.203.239.145.in-addr.arpa domain name pointer ip138.ip-145-239-203.eu.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
138.203.239.145.in-addr.arpa	name = ip138.ip-145-239-203.eu.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
31.145.204.87 attackspam
2019-11-01T07:03:07.041Z CLOSE host=31.145.204.87 port=46319 fd=4 time=20.018 bytes=22
...
2020-03-13 05:09:57
190.239.192.167 attack
20/3/12@17:12:14: FAIL: Alarm-Network address from=190.239.192.167
...
2020-03-13 05:37:24
31.18.189.41 attackbots
2019-12-14T00:30:54.684Z CLOSE host=31.18.189.41 port=53394 fd=4 time=20.020 bytes=7
...
2020-03-13 05:10:19
103.72.8.7 attackspambots
Mar1222:12:58server2kernel:Firewall:\*TCP_INBlocked\*IN=eth0OUT=MAC=00:16:3e:3f:7a:43:52:54:00:a2:7f:43:08:00SRC=103.72.8.7DST=136.243.224.52LEN=44TOS=0x00PREC=0x00TTL=241ID=7661PROTO=TCPSPT=54624DPT=21718WINDOW=1024RES=0x00SYNURGP=0Mar1222:13:00server2kernel:Firewall:\*TCP_INBlocked\*IN=eth0OUT=MAC=00:16:3e:3f:7a:43:52:54:00:a2:7f:43:08:00SRC=103.72.8.7DST=136.243.224.54LEN=44TOS=0x00PREC=0x00TTL=241ID=1249PROTO=TCPSPT=54624DPT=20333WINDOW=1024RES=0x00SYNURGP=0Mar1222:13:04server2kernel:Firewall:\*TCP_INBlocked\*IN=eth0OUT=MAC=00:16:3e:3f:7a:43:52:54:00:a2:7f:43:08:00SRC=103.72.8.7DST=136.243.224.56LEN=44TOS=0x00PREC=0x00TTL=241ID=23435PROTO=TCPSPT=54624DPT=20533WINDOW=1024RES=0x00SYNURGP=0Mar1222:13:06server2kernel:Firewall:\*TCP_INBlocked\*IN=eth0OUT=MAC=00:16:3e:3f:7a:43:52:54:00:a2:7f:43:08:00SRC=103.72.8.7DST=136.243.224.57LEN=44TOS=0x00PREC=0x00TTL=241ID=16912PROTO=TCPSPT=54624DPT=20992WINDOW=1024RES=0x00SYNURGP=0Mar1222:13:13server2kernel:Firewall:\*TCP_INBlocked\*IN=eth0OUT=MAC=00:16:3e:3f:7a:43:52:5
2020-03-13 05:27:29
45.151.254.218 attackspam
User Datagram Protocol, Src Port: tag-pm (5073), Dst Port: sip (5060)
From: "sipvicious";tag=6332613061383837313363340133353837303938303035
Accept: application/sdp
User-Agent: friendly-scanner
To: "sipvicious"
Contact: sip:100@45.151.254.218:5073
CSeq: 1 OPTIONS
Call-ID: 266344954241521547702694
https://www.virustotal.com/graph/embed/g88e60c19fe254cfa95de7adcfcb753a73b0346a99a364302b266225f9744f71c
https://github.com/rapid7/metasploit-framework/blob/master/modules/exploits/multi/http/splunk_upload_app_exec.rb
----------------
xxx.xxx.xxx.xxx 192.168.0.1	DNS 88	Standard query 0x9475 PTR xxx.xxx.xxx.xxx-addr.arpa & retrans Q
unicast multiprobe UDP 137 mmcc(5050) → mmcc(5050) Len=95 /96 / 99 ...
multicast  multiprobe 239.255.255.250	UDP 85	mmcc(5050) → mmcc(5050) Len=43
broadcast mutiprobe  xxx.xxx.xxx.255 UDP 85	mmcc(5050) → mmcc(5050) Len=43
2020-03-13 05:38:55
36.71.53.217 attack
2020-03-10T15:59:00.573Z CLOSE host=36.71.53.217 port=59072 fd=5 time=20.005 bytes=18
...
2020-03-13 05:03:53
36.85.63.167 attackspam
Automatic report - Port Scan Attack
2020-03-13 05:23:03
212.47.240.88 attackspam
Mar 12 18:08:55 firewall sshd[5666]: Failed password for invalid user libuuid from 212.47.240.88 port 36808 ssh2
Mar 12 18:12:42 firewall sshd[5755]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.47.240.88  user=root
Mar 12 18:12:43 firewall sshd[5755]: Failed password for root from 212.47.240.88 port 54432 ssh2
...
2020-03-13 05:14:23
36.71.239.106 attackspam
2020-02-24T14:02:41.676Z CLOSE host=36.71.239.106 port=62608 fd=4 time=20.004 bytes=15
...
2020-03-13 05:04:17
159.65.102.98 attackbots
Automatically reported by fail2ban report script (mx1)
2020-03-13 05:34:04
200.89.178.140 attack
Mar 12 22:12:44  sshd\[21631\]: Invalid user team1 from 200.89.178.140Mar 12 22:12:47  sshd\[21631\]: Failed password for invalid user team1 from 200.89.178.140 port 56154 ssh2
...
2020-03-13 05:12:50
152.32.172.54 attackspambots
SSH Authentication Attempts Exceeded
2020-03-13 05:00:47
104.248.139.121 attack
Mar 12 22:09:47 legacy sshd[17921]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.139.121
Mar 12 22:09:49 legacy sshd[17921]: Failed password for invalid user james from 104.248.139.121 port 55428 ssh2
Mar 12 22:13:29 legacy sshd[17991]: Failed password for root from 104.248.139.121 port 43464 ssh2
...
2020-03-13 05:24:16
123.201.95.215 attack
Unauthorized connection attempt detected from IP address 123.201.95.215 to port 23
2020-03-13 05:22:14
142.93.172.67 attack
Automatic report - SSH Brute-Force Attack
2020-03-13 05:13:03

Recently Reported IPs

99.159.239.240 185.50.107.155 37.134.254.195 9.254.210.86
132.117.150.63 30.234.95.32 2.207.236.254 28.182.105.119
3.216.97.49 69.27.171.13 38.244.208.214 20.201.82.94
236.241.198.144 79.172.84.230 42.114.139.92 198.80.235.118
154.171.73.27 109.125.141.123 113.38.79.122 135.35.191.95