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

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

;; QUESTION SECTION:
;85.48.7.109.			IN	A

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

;; Query time: 13 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Nov 18 00:29:05 CST 2024
;; MSG SIZE  rcvd: 104
Host info
109.7.48.85.in-addr.arpa domain name pointer 109.pool85-48-7.dynamic.orange.es.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
109.7.48.85.in-addr.arpa	name = 109.pool85-48-7.dynamic.orange.es.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
134.228.154.244 attackspambots
Automatic report - Port Scan Attack
2019-12-03 14:40:40
178.62.82.240 attackbots
Port 22 Scan, PTR: None
2019-12-03 15:15:45
132.232.7.197 attack
Dec  2 20:44:54 sachi sshd\[14881\]: Invalid user gdm from 132.232.7.197
Dec  2 20:44:54 sachi sshd\[14881\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=132.232.7.197
Dec  2 20:44:57 sachi sshd\[14881\]: Failed password for invalid user gdm from 132.232.7.197 port 42870 ssh2
Dec  2 20:52:28 sachi sshd\[15544\]: Invalid user prosper from 132.232.7.197
Dec  2 20:52:28 sachi sshd\[15544\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=132.232.7.197
2019-12-03 14:58:15
129.211.147.91 attack
2019-12-03T06:29:54.487295abusebot-8.cloudsearch.cf sshd\[14678\]: Invalid user webadmin from 129.211.147.91 port 59586
2019-12-03 14:55:39
218.92.0.158 attack
SSHScan
2019-12-03 14:43:43
51.159.1.3 attackbotsspam
Port 22 Scan, PTR: None
2019-12-03 14:50:14
52.203.197.242 attackbots
2019-12-03T06:20:28.790103shield sshd\[19958\]: Invalid user dorcey from 52.203.197.242 port 53725
2019-12-03T06:20:28.794445shield sshd\[19958\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ec2-52-203-197-242.compute-1.amazonaws.com
2019-12-03T06:20:30.754161shield sshd\[19958\]: Failed password for invalid user dorcey from 52.203.197.242 port 53725 ssh2
2019-12-03T06:29:51.356481shield sshd\[22771\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ec2-52-203-197-242.compute-1.amazonaws.com  user=root
2019-12-03T06:29:52.938063shield sshd\[22771\]: Failed password for root from 52.203.197.242 port 59997 ssh2
2019-12-03 14:59:00
39.90.66.105 attackbotsspam
39.90.66.105 was recorded 5 times by 5 hosts attempting to connect to the following ports: 123. Incident counter (4h, 24h, all-time): 5, 6, 10
2019-12-03 14:45:09
94.152.193.14 attackbotsspam
SpamReport
2019-12-03 14:41:40
128.199.247.115 attackspambots
Dec  3 08:00:19 mail sshd[16269]: Failed password for root from 128.199.247.115 port 49182 ssh2
Dec  3 08:06:41 mail sshd[17916]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.247.115 
Dec  3 08:06:43 mail sshd[17916]: Failed password for invalid user server from 128.199.247.115 port 59992 ssh2
2019-12-03 15:12:49
89.187.165.112 attackspambots
Brute force attempt
2019-12-03 15:06:53
112.85.42.173 attackspam
Dec  3 08:02:19 mail sshd[16738]: Failed password for root from 112.85.42.173 port 24295 ssh2
Dec  3 08:02:23 mail sshd[16738]: Failed password for root from 112.85.42.173 port 24295 ssh2
Dec  3 08:02:27 mail sshd[16738]: Failed password for root from 112.85.42.173 port 24295 ssh2
Dec  3 08:02:32 mail sshd[16738]: Failed password for root from 112.85.42.173 port 24295 ssh2
2019-12-03 15:07:57
137.74.5.149 attack
Dec  2 01:43:09 ahost sshd[21150]: Address 137.74.5.149 maps to lemon.click, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Dec  2 01:43:09 ahost sshd[21150]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=137.74.5.149  user=r.r
Dec  2 01:43:11 ahost sshd[21150]: Failed password for r.r from 137.74.5.149 port 33282 ssh2
Dec  2 01:43:11 ahost sshd[21150]: Received disconnect from 137.74.5.149: 11: Bye Bye [preauth]
Dec  2 01:50:40 ahost sshd[21231]: Address 137.74.5.149 maps to lemon.click, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Dec  2 01:50:40 ahost sshd[21231]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=137.74.5.149  user=r.r
Dec  2 01:50:42 ahost sshd[21231]: Failed password for r.r from 137.74.5.149 port 53198 ssh2
Dec  2 01:50:42 ahost sshd[21231]: Received disconnect from 137.74.5.149: 11: Bye Bye [preauth]
Dec  2 01:56:03 aho........
------------------------------
2019-12-03 14:52:44
118.70.190.188 attackbots
Dec  3 07:29:48 vpn01 sshd[26211]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.70.190.188
Dec  3 07:29:50 vpn01 sshd[26211]: Failed password for invalid user denise1 from 118.70.190.188 port 42216 ssh2
...
2019-12-03 15:02:04
222.186.175.140 attackbots
$f2bV_matches
2019-12-03 15:07:12

Recently Reported IPs

39.30.207.243 205.195.243.128 31.57.248.154 245.140.226.13
109.231.61.204 242.222.1.190 224.2.197.215 203.34.232.18
45.196.204.247 22.214.24.93 40.223.81.6 225.225.131.97
149.120.118.95 103.153.91.73 119.244.40.67 50.9.180.37
174.114.52.16 96.163.20.65 150.100.154.145 90.71.184.179