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: United States

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

;; QUESTION SECTION:
;130.80.30.55.			IN	A

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

;; Query time: 68 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Oct 08 00:31:52 CST 2023
;; MSG SIZE  rcvd: 105
Host info
Host 55.30.80.130.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 55.30.80.130.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
193.112.191.228 attack
Sep 26 07:25:09 localhost sshd\[67876\]: Invalid user t from 193.112.191.228 port 60644
Sep 26 07:25:09 localhost sshd\[67876\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.112.191.228
Sep 26 07:25:11 localhost sshd\[67876\]: Failed password for invalid user t from 193.112.191.228 port 60644 ssh2
Sep 26 07:27:46 localhost sshd\[67962\]: Invalid user alysha from 193.112.191.228 port 56084
Sep 26 07:27:46 localhost sshd\[67962\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.112.191.228
...
2019-09-26 17:08:45
193.112.164.113 attackbots
Sep 26 10:44:30 vps691689 sshd[9305]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.112.164.113
Sep 26 10:44:32 vps691689 sshd[9305]: Failed password for invalid user schopenhauer from 193.112.164.113 port 38452 ssh2
...
2019-09-26 17:00:57
122.227.185.101 attackspambots
Sep 25 23:46:56 localhost kernel: [3207434.321816] iptables_INPUT_denied: IN=eth0 OUT= MAC=f2:3c:91:84:83:95:84:78:ac:57:a8:41:08:00 SRC=122.227.185.101 DST=[mungedIP2] LEN=40 TOS=0x08 PREC=0x20 TTL=235 ID=42788 PROTO=TCP SPT=52366 DPT=445 WINDOW=1024 RES=0x00 SYN URGP=0 
Sep 25 23:46:56 localhost kernel: [3207434.321841] iptables_INPUT_denied: IN=eth0 OUT= MAC=f2:3c:91:84:83:95:84:78:ac:57:a8:41:08:00 SRC=122.227.185.101 DST=[mungedIP2] LEN=40 TOS=0x08 PREC=0x20 TTL=235 ID=42788 PROTO=TCP SPT=52366 DPT=445 SEQ=1638057703 ACK=0 WINDOW=1024 RES=0x00 SYN URGP=0
2019-09-26 17:01:31
202.163.110.162 attack
Attempt to attack host OS, exploiting network vulnerabilities, on 26-09-2019 04:45:30.
2019-09-26 17:37:38
45.136.109.199 attackbotsspam
09/26/2019-05:13:15.728101 45.136.109.199 Protocol: 6 ET SCAN NMAP -sS window 1024
2019-09-26 17:28:18
77.42.118.155 attackbots
Automatic report - Port Scan Attack
2019-09-26 16:59:37
79.188.250.213 attackbots
Sep 24 16:10:35 localhost kernel: [3093653.499564] iptables_INPUT_denied: IN=eth0 OUT= MAC=f2:3c:91:84:83:95:84:78:ac:57:aa:c1:08:00 SRC=79.188.250.213 DST=[mungedIP2] LEN=44 TOS=0x00 PREC=0x00 TTL=53 ID=19316 PROTO=TCP SPT=49699 DPT=52869 WINDOW=29346 RES=0x00 SYN URGP=0 
Sep 24 16:10:35 localhost kernel: [3093653.499595] iptables_INPUT_denied: IN=eth0 OUT= MAC=f2:3c:91:84:83:95:84:78:ac:57:aa:c1:08:00 SRC=79.188.250.213 DST=[mungedIP2] LEN=44 TOS=0x00 PREC=0x00 TTL=53 ID=19316 PROTO=TCP SPT=49699 DPT=52869 SEQ=758669438 ACK=0 WINDOW=29346 RES=0x00 SYN URGP=0 OPT (020405B4) 
Sep 25 23:45:49 localhost kernel: [3207367.775963] iptables_INPUT_denied: IN=eth0 OUT= MAC=f2:3c:91:84:83:95:84:78:ac:57:aa:c1:08:00 SRC=79.188.250.213 DST=[mungedIP2] LEN=44 TOS=0x00 PREC=0x00 TTL=53 ID=17328 PROTO=TCP SPT=36443 DPT=52869 WINDOW=56579 RES=0x00 SYN URGP=0 
Sep 25 23:45:49 localhost kernel: [3207367.775989] iptables_INPUT_denied: IN=eth0 OUT= MAC=f2:3c:91:84:83:95:84:78:ac:57:aa:c1:08:00 SRC=79.188.250.213 DST=[mungedIP2]
2019-09-26 17:22:37
189.147.110.167 attackspam
Attempt to attack host OS, exploiting network vulnerabilities, on 26-09-2019 04:45:29.
2019-09-26 17:40:17
121.234.105.113 attackbotsspam
Sep 24 03:17:43 web1 sshd[22462]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.234.105.113  user=r.r
Sep 24 03:17:45 web1 sshd[22462]: Failed password for r.r from 121.234.105.113 port 64874 ssh2
Sep 24 03:17:49 web1 sshd[22462]: Failed password for r.r from 121.234.105.113 port 64874 ssh2
Sep 24 03:17:55 web1 sshd[22462]: Failed password for r.r from 121.234.105.113 port 64874 ssh2
Sep 24 03:17:58 web1 sshd[22462]: Failed password for r.r from 121.234.105.113 port 64874 ssh2
Sep 24 03:18:01 web1 sshd[22462]: Failed password for r.r from 121.234.105.113 port 64874 ssh2
Sep 24 03:18:07 web1 sshd[22462]: Failed password for r.r from 121.234.105.113 port 64874 ssh2
Sep 24 03:18:07 web1 sshd[22462]: PAM 5 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.234.105.113  user=r.r


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=121.234.105.113
2019-09-26 17:02:41
81.171.58.182 attack
\[2019-09-26 09:30:40\] NOTICE\[14660\] res_pjsip/pjsip_distributor.c: Request 'REGISTER' from '\' failed for '81.171.58.182:64769' \(callid: 1832784954-1306307298-904183106\) - Failed to authenticate
\[2019-09-26 09:30:40\] SECURITY\[1715\] res_security_log.c: SecurityEvent="ChallengeResponseFailed",EventTV="2019-09-26T09:30:40.589+0200",Severity="Error",Service="PJSIP",EventVersion="1",AccountID="\",SessionID="1832784954-1306307298-904183106",LocalAddress="IPV4/UDP/188.40.118.248/5060",RemoteAddress="IPV4/UDP/81.171.58.182/64769",Challenge="1569483040/bdf4b8ac73d03971941b75372ea2e590",Response="f1ef8db92c3dae3a26db31ca2df0a096",ExpectedResponse=""
\[2019-09-26 09:30:40\] NOTICE\[25634\] res_pjsip/pjsip_distributor.c: Request 'REGISTER' from '\' failed for '81.171.58.182:64769' \(callid: 1832784954-1306307298-904183106\) - Failed to authenticate
\[2019-09-26 09:30:40\] SECURITY\[1715\] res_security_log.c: SecurityEvent="ChallengeResponseF
2019-09-26 16:57:07
106.111.166.26 attack
Sep 22 08:45:47 josie sshd[18294]: Invalid user service from 106.111.166.26
Sep 22 08:45:47 josie sshd[18294]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.111.166.26 
Sep 22 08:45:48 josie sshd[18294]: Failed password for invalid user service from 106.111.166.26 port 54213 ssh2
Sep 22 08:45:52 josie sshd[18294]: Failed password for invalid user service from 106.111.166.26 port 54213 ssh2
Sep 22 08:45:56 josie sshd[18294]: Failed password for invalid user service from 106.111.166.26 port 54213 ssh2
Sep 22 08:46:00 josie sshd[18294]: Failed password for invalid user service from 106.111.166.26 port 54213 ssh2
Sep 22 08:46:04 josie sshd[18294]: Failed password for invalid user service from 106.111.166.26 port 54213 ssh2
Sep 25 11:50:04 josie sshd[4888]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.111.166.26  user=r.r
Sep 25 11:50:07 josie sshd[4888]: Failed password for r.r from........
-------------------------------
2019-09-26 17:08:15
52.37.77.112 attackspambots
Sending out Netflix spam from IP 54.240.14.174 
(amazon.com / amazonaws.com) 

I have NEVER been a Netflix customer and
never asked for this junk. 

The website spammed out is 

https://www.netflix.com/signup/creditoption?nftoken=BQAbAAEBEA77T6CHfer3tv8qolkSAduAkLFC%2FFYUyiUS4Sdi62TDOAptLP7WiMxUQK74rIuN%2BRXrWDnwU8vxCNSC2khWG0ZmflN2tsqMsqNHMDWRdKmlf6XFVqwlgd%2BFLY2Nz88IH4y3pcuOeFYD5X9L4G9ZZfbRHvrmZF%2FjsAyUI1f5mpTFg3eEFWfNQayYDiVrbb%2FU65EF%2B0XXrVI0T4jKa2zmCB8w5g%3D%3D&lnktrk=EMP&g=AEF2F71097E503EBEB44921E2720235C64526E40&lkid=URL_SIGNUP_CREDIT
IPs: 54.69.16.110, 54.70.73.70, 54.149.101.155,
54.201.91.38, 54.213.182.74, 52.37.77.112,
52.41.20.47, 52.41.193.16
(amazon.com / amazonaws.com) 

amazon are pure scumbags who allow their 
customers to send out spam and do nothing 
about it! 
Report via email and website at 
https://support.aws.amazon.com/#/contacts/report-abuse
2019-09-26 17:32:18
119.96.227.19 attack
Sep 26 08:48:28 DAAP sshd[14800]: Invalid user rt from 119.96.227.19 port 55658
Sep 26 08:48:28 DAAP sshd[14800]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.96.227.19
Sep 26 08:48:28 DAAP sshd[14800]: Invalid user rt from 119.96.227.19 port 55658
Sep 26 08:48:30 DAAP sshd[14800]: Failed password for invalid user rt from 119.96.227.19 port 55658 ssh2
...
2019-09-26 17:35:51
193.56.28.178 attack
Sep 26 10:35:01 mail postfix/smtpd\[11047\]: warning: unknown\[193.56.28.178\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\
Sep 26 10:35:07 mail postfix/smtpd\[11047\]: warning: unknown\[193.56.28.178\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\
Sep 26 10:35:17 mail postfix/smtpd\[11047\]: warning: unknown\[193.56.28.178\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\
Sep 26 10:35:27 mail postfix/smtpd\[11047\]: warning: unknown\[193.56.28.178\]: SASL LOGIN authentication failed: Connection lost to authentication server\
2019-09-26 17:03:03
212.98.162.206 attackbots
Attempt to attack host OS, exploiting network vulnerabilities, on 26-09-2019 04:45:31.
2019-09-26 17:37:21

Recently Reported IPs

90.230.173.192 175.84.88.148 35.213.14.149 240.45.63.11
239.64.143.142 166.85.191.106 56.159.147.253 164.117.64.57
242.12.90.172 214.23.130.82 119.133.241.189 169.76.29.94
143.127.200.151 40.175.126.247 48.24.191.15 223.30.17.230
52.178.148.231 222.169.67.105 225.111.79.56 95.64.21.247