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

;; QUESTION SECTION:
;44.202.30.80.			IN	A

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

;; Query time: 61 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 13 11:21:29 CST 2022
;; MSG SIZE  rcvd: 105
Host info
80.30.202.44.in-addr.arpa domain name pointer ec2-44-202-30-80.compute-1.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
80.30.202.44.in-addr.arpa	name = ec2-44-202-30-80.compute-1.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
125.64.94.201 attackbots
CloudCIX Reconnaissance Scan Detected, PTR: PTR record not found
2019-11-06 21:14:03
198.55.103.47 attackspambots
CloudCIX Reconnaissance Scan Detected, PTR: 198.55.103.47.static.quadranet.com.
2019-11-06 21:18:11
140.143.242.159 attack
Nov  6 14:14:36 MK-Soft-Root2 sshd[1451]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.242.159 
Nov  6 14:14:38 MK-Soft-Root2 sshd[1451]: Failed password for invalid user Test@2018 from 140.143.242.159 port 36952 ssh2
...
2019-11-06 21:17:26
52.167.54.97 attackbotsspam
failed_logins
2019-11-06 21:23:42
212.83.138.75 attackspambots
$f2bV_matches
2019-11-06 21:04:50
178.62.214.85 attackbots
Nov  6 03:16:16 ny01 sshd[14718]: Failed password for root from 178.62.214.85 port 54930 ssh2
Nov  6 03:20:14 ny01 sshd[15092]: Failed password for root from 178.62.214.85 port 46048 ssh2
2019-11-06 21:22:25
94.191.2.228 attackspambots
Automatic report - Banned IP Access
2019-11-06 21:15:08
81.182.254.124 attack
Nov  6 12:37:50 server sshd\[8739\]: Invalid user eran from 81.182.254.124
Nov  6 12:37:50 server sshd\[8739\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=dsl51b6fe7c.fixip.t-online.hu 
Nov  6 12:37:53 server sshd\[8739\]: Failed password for invalid user eran from 81.182.254.124 port 53316 ssh2
Nov  6 12:53:10 server sshd\[12624\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=dsl51b6fe7c.fixip.t-online.hu  user=root
Nov  6 12:53:12 server sshd\[12624\]: Failed password for root from 81.182.254.124 port 40016 ssh2
...
2019-11-06 21:14:29
46.161.27.130 attackspam
Password spraying hacking attempt via VPN
2019-11-06 21:24:06
209.85.166.194 attack
Received:  from tgl-28-oktober-rangga-400k-fb (221.108.226.35.bc.googleusercontent.com. [35.226.108.221]) by smtp.gmail.com with ESMTPSA id k24sm1949411ioa.3.2019.11.05.17.02.05 
host 35.226.108.221 (getting name) = 221.108.226.35.bc.googleusercontent.com.
221.108.226.35.bc.googleusercontent.com is 35.226.108.221
RE: "update statement on account" = BOGUS SPAM
IP 209.85.166.194 Abusive JUNK SCAM
2019-11-06 21:17:50
213.87.126.109 attack
Chat Spam
2019-11-06 20:51:47
49.88.112.74 attackspambots
Nov  6 11:53:35 vmi181237 sshd\[16195\]: refused connect from 49.88.112.74 \(49.88.112.74\)
Nov  6 11:54:39 vmi181237 sshd\[16223\]: refused connect from 49.88.112.74 \(49.88.112.74\)
Nov  6 11:55:32 vmi181237 sshd\[16249\]: refused connect from 49.88.112.74 \(49.88.112.74\)
Nov  6 11:56:24 vmi181237 sshd\[16269\]: refused connect from 49.88.112.74 \(49.88.112.74\)
Nov  6 11:57:15 vmi181237 sshd\[16291\]: refused connect from 49.88.112.74 \(49.88.112.74\)
2019-11-06 21:15:39
185.153.196.28 attack
Nov  6 12:47:46 mc1 kernel: \[4327165.732855\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=185.153.196.28 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=40613 PROTO=TCP SPT=52736 DPT=1122 WINDOW=1024 RES=0x00 SYN URGP=0 
Nov  6 12:52:39 mc1 kernel: \[4327458.419033\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=185.153.196.28 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=19064 PROTO=TCP SPT=52736 DPT=27 WINDOW=1024 RES=0x00 SYN URGP=0 
Nov  6 12:56:23 mc1 kernel: \[4327682.492612\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=185.153.196.28 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=48160 PROTO=TCP SPT=52736 DPT=1255 WINDOW=1024 RES=0x00 SYN URGP=0 
...
2019-11-06 21:11:21
159.65.239.48 attackbots
$f2bV_matches
2019-11-06 20:50:37
94.99.138.141 attackspam
Lines containing failures of 94.99.138.141
Nov  6 07:18:08 server01 postfix/smtpd[7390]: connect from unknown[94.99.138.141]
Nov x@x
Nov x@x
Nov  6 07:18:10 server01 postfix/policy-spf[7400]: : Policy action=PREPEND Received-SPF: none (elinsurance.com: No applicable sender policy available) receiver=x@x
Nov x@x
Nov  6 07:18:11 server01 postfix/smtpd[7390]: lost connection after DATA from unknown[94.99.138.141]
Nov  6 07:18:11 server01 postfix/smtpd[7390]: disconnect from unknown[94.99.138.141]


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=94.99.138.141
2019-11-06 21:03:30

Recently Reported IPs

44.242.181.196 45.10.166.100 45.115.112.194 45.112.251.15
45.117.207.165 45.10.167.165 45.112.251.8 45.118.9.21
45.114.90.18 45.12.108.251 45.112.251.29 45.116.68.21
45.113.239.68 45.120.49.6 45.120.2.97 45.121.237.148
45.122.48.144 45.121.209.165 45.120.17.3 45.121.236.143