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

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;81.42.48.218.			IN	A

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

;; Query time: 266 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Nov 01 12:41:41 CST 2019
;; MSG SIZE  rcvd: 116
Host info
218.48.42.81.in-addr.arpa domain name pointer 218.red-81-42-48.staticip.rima-tde.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
218.48.42.81.in-addr.arpa	name = 218.red-81-42-48.staticip.rima-tde.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
138.197.25.187 attackbots
Repeated brute force against a port
2019-12-29 06:13:02
82.81.24.133 attackbotsspam
Automatic report - Banned IP Access
2019-12-29 06:22:45
114.44.190.56 attackbotsspam
Unauthorized connection attempt detected from IP address 114.44.190.56 to port 1433
2019-12-29 05:57:20
45.136.108.116 attackspam
Dec 28 22:41:19 h2177944 kernel: \[767970.454368\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=45.136.108.116 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=249 ID=40115 PROTO=TCP SPT=49821 DPT=1058 WINDOW=1024 RES=0x00 SYN URGP=0 
Dec 28 22:41:19 h2177944 kernel: \[767970.454382\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=45.136.108.116 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=249 ID=40115 PROTO=TCP SPT=49821 DPT=1058 WINDOW=1024 RES=0x00 SYN URGP=0 
Dec 28 22:56:27 h2177944 kernel: \[768878.125124\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=45.136.108.116 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=249 ID=2447 PROTO=TCP SPT=49821 DPT=6090 WINDOW=1024 RES=0x00 SYN URGP=0 
Dec 28 22:56:27 h2177944 kernel: \[768878.125139\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=45.136.108.116 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=249 ID=2447 PROTO=TCP SPT=49821 DPT=6090 WINDOW=1024 RES=0x00 SYN URGP=0 
Dec 28 22:58:03 h2177944 kernel: \[768974.334568\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=45.136.108.116 DST=85.214.117.9 L
2019-12-29 06:06:06
104.236.239.60 attackspam
Dec 28 04:24:17 server sshd\[14446\]: Failed password for invalid user mailer from 104.236.239.60 port 45183 ssh2
Dec 28 22:41:59 server sshd\[7655\]: Invalid user www-ssl from 104.236.239.60
Dec 28 22:41:59 server sshd\[7655\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.236.239.60 
Dec 28 22:42:01 server sshd\[7655\]: Failed password for invalid user www-ssl from 104.236.239.60 port 49726 ssh2
Dec 28 22:45:15 server sshd\[8390\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.236.239.60  user=root
...
2019-12-29 05:58:25
115.90.219.20 attack
Dec 28 16:32:10 work-partkepr sshd\[8695\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=115.90.219.20  user=root
Dec 28 16:32:12 work-partkepr sshd\[8695\]: Failed password for root from 115.90.219.20 port 49576 ssh2
...
2019-12-29 06:21:29
167.114.192.162 attack
Invalid user ripley from 167.114.192.162 port 22623
2019-12-29 05:44:20
156.67.250.205 attack
Dec 28 21:48:10 ns3110291 sshd\[4817\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=156.67.250.205  user=root
Dec 28 21:48:13 ns3110291 sshd\[4817\]: Failed password for root from 156.67.250.205 port 36276 ssh2
Dec 28 21:48:44 ns3110291 sshd\[4833\]: Invalid user satan from 156.67.250.205
Dec 28 21:48:44 ns3110291 sshd\[4833\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=156.67.250.205 
Dec 28 21:48:46 ns3110291 sshd\[4833\]: Failed password for invalid user satan from 156.67.250.205 port 39890 ssh2
...
2019-12-29 06:22:00
187.111.210.137 attackspambots
Dec 28 16:23:29 site1 sshd\[60796\]: Failed password for root from 187.111.210.137 port 44777 ssh2Dec 28 16:23:51 site1 sshd\[60815\]: Failed password for root from 187.111.210.137 port 44796 ssh2Dec 28 16:24:12 site1 sshd\[60852\]: Failed password for root from 187.111.210.137 port 44812 ssh2Dec 28 16:24:33 site1 sshd\[60864\]: Failed password for root from 187.111.210.137 port 44829 ssh2Dec 28 16:24:46 site1 sshd\[60872\]: Invalid user admin from 187.111.210.137Dec 28 16:24:48 site1 sshd\[60872\]: Failed password for invalid user admin from 187.111.210.137 port 44841 ssh2
...
2019-12-29 05:52:00
198.211.120.59 attackbotsspam
12/28/2019-23:12:01.011855 198.211.120.59 Protocol: 17 ET INFO Session Traversal Utilities for NAT (STUN Binding Response)
2019-12-29 06:18:17
80.82.64.127 attack
Unauthorised access (Dec 29) SRC=80.82.64.127 LEN=40 PREC=0x20 TTL=250 ID=40165 TCP DPT=3306 WINDOW=1024 SYN 
Unauthorised access (Dec 27) SRC=80.82.64.127 LEN=40 PREC=0x20 TTL=250 ID=56459 TCP DPT=3389 WINDOW=1024 SYN 
Unauthorised access (Dec 23) SRC=80.82.64.127 LEN=40 PREC=0x20 TTL=250 ID=27679 TCP DPT=8080 WINDOW=1024 SYN
2019-12-29 06:08:12
23.126.140.33 attackspam
Dec 28 11:58:14 web9 sshd\[15339\]: Invalid user nanashi from 23.126.140.33
Dec 28 11:58:14 web9 sshd\[15339\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=23.126.140.33
Dec 28 11:58:16 web9 sshd\[15339\]: Failed password for invalid user nanashi from 23.126.140.33 port 2185 ssh2
Dec 28 12:05:37 web9 sshd\[16405\]: Invalid user arnesson from 23.126.140.33
Dec 28 12:05:37 web9 sshd\[16405\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=23.126.140.33
2019-12-29 06:09:44
180.244.28.235 attackbots
none
2019-12-29 05:58:04
39.35.55.23 attackbotsspam
Dec 28 15:24:36 grey postfix/smtpd\[9104\]: NOQUEUE: reject: RCPT from unknown\[39.35.55.23\]: 554 5.7.1 Service unavailable\; Client host \[39.35.55.23\] blocked using bl.spamcop.net\; Blocked - see https://www.spamcop.net/bl.shtml\?39.35.55.23\; from=\ to=\ proto=ESMTP helo=\<\[39.35.55.23\]\>
...
2019-12-29 05:58:46
134.175.46.166 attackbotsspam
Dec 28 22:57:37 tuxlinux sshd[47518]: Invalid user au from 134.175.46.166 port 37852
Dec 28 22:57:37 tuxlinux sshd[47518]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.175.46.166 
Dec 28 22:57:37 tuxlinux sshd[47518]: Invalid user au from 134.175.46.166 port 37852
Dec 28 22:57:37 tuxlinux sshd[47518]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.175.46.166 
Dec 28 22:57:37 tuxlinux sshd[47518]: Invalid user au from 134.175.46.166 port 37852
Dec 28 22:57:37 tuxlinux sshd[47518]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.175.46.166 
Dec 28 22:57:40 tuxlinux sshd[47518]: Failed password for invalid user au from 134.175.46.166 port 37852 ssh2
...
2019-12-29 06:20:41

Recently Reported IPs

90.173.124.79 97.231.22.193 150.19.111.224 238.81.183.46
107.56.171.197 173.45.46.27 143.224.26.127 26.238.66.51
55.63.229.254 195.238.237.142 3.168.112.63 27.207.150.214
79.187.125.229 74.110.211.43 245.137.251.87 3.168.48.227
91.214.111.56 237.235.168.104 220.175.149.101 117.242.81.182