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

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

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

;; Query time: 51 msec
;; SERVER: 67.207.67.3#53(67.207.67.3)
;; WHEN: Mon May 06 07:31:29 +08 2019
;; MSG SIZE  rcvd: 117

Host info
54.245.140.18.in-addr.arpa domain name pointer ec2-18-140-245-54.ap-southeast-1.compute.amazonaws.com.
Nslookup info:
Server:		67.207.67.3
Address:	67.207.67.3#53

Non-authoritative answer:
54.245.140.18.in-addr.arpa	name = ec2-18-140-245-54.ap-southeast-1.compute.amazonaws.com.

Authoritative answers can be found from:

Related IP info:
Related comments:
IP Type Details Datetime
36.90.255.241 attackspambots
Attempt to attack host OS, exploiting network vulnerabilities, on 26-09-2019 04:45:33.
2019-09-26 17:33:10
94.191.122.49 attackbots
Automatic report - Banned IP Access
2019-09-26 17:23:30
52.186.168.121 attack
Sep 26 07:28:22 eventyay sshd[1885]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=52.186.168.121
Sep 26 07:28:24 eventyay sshd[1885]: Failed password for invalid user ibm from 52.186.168.121 port 60932 ssh2
Sep 26 07:32:40 eventyay sshd[1940]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=52.186.168.121
...
2019-09-26 17:15:04
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
85.140.38.90 attack
Sep 26 05:41:27 reporting6 sshd[21960]: reveeclipse mapping checking getaddrinfo for 38-90.izhnt.ru [85.140.38.90] failed - POSSIBLE BREAK-IN ATTEMPT!
Sep 26 05:41:27 reporting6 sshd[21960]: User r.r from 85.140.38.90 not allowed because not listed in AllowUsers
Sep 26 05:41:27 reporting6 sshd[21960]: Failed password for invalid user r.r from 85.140.38.90 port 33779 ssh2
Sep 26 05:41:27 reporting6 sshd[21960]: Failed password for invalid user r.r from 85.140.38.90 port 33779 ssh2
Sep 26 05:41:27 reporting6 sshd[21960]: Failed password for invalid user r.r from 85.140.38.90 port 33779 ssh2
Sep 26 05:41:27 reporting6 sshd[21960]: Failed password for invalid user r.r from 85.140.38.90 port 33779 ssh2
Sep 26 05:41:27 reporting6 sshd[21960]: Failed password for invalid user r.r from 85.140.38.90 port 33779 ssh2
Sep 26 05:41:28 reporting6 sshd[21960]: Failed password for invalid user r.r from 85.140.38.90 port 33779 ssh2
Sep 26 05:41:34 reporting6 sshd[22052]: reveeclipse map........
-------------------------------
2019-09-26 17:15:38
116.192.241.123 attackbotsspam
Sep 26 03:22:43 TORMINT sshd\[25225\]: Invalid user bf3server from 116.192.241.123
Sep 26 03:22:43 TORMINT sshd\[25225\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.192.241.123
Sep 26 03:22:45 TORMINT sshd\[25225\]: Failed password for invalid user bf3server from 116.192.241.123 port 17793 ssh2
...
2019-09-26 17:07:45
222.186.180.41 attackbots
Sep 25 23:01:23 hiderm sshd\[29593\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.41  user=root
Sep 25 23:01:25 hiderm sshd\[29593\]: Failed password for root from 222.186.180.41 port 22658 ssh2
Sep 25 23:01:51 hiderm sshd\[29632\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.41  user=root
Sep 25 23:01:53 hiderm sshd\[29632\]: Failed password for root from 222.186.180.41 port 61930 ssh2
Sep 25 23:02:05 hiderm sshd\[29632\]: Failed password for root from 222.186.180.41 port 61930 ssh2
2019-09-26 17:09:17
43.226.39.221 attackspam
Sep 26 04:29:25 game-panel sshd[1185]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=43.226.39.221
Sep 26 04:29:27 game-panel sshd[1185]: Failed password for invalid user ee from 43.226.39.221 port 36654 ssh2
Sep 26 04:32:46 game-panel sshd[1266]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=43.226.39.221
2019-09-26 17:21:08
129.213.122.26 attackbots
Lines containing failures of 129.213.122.26
Sep 24 05:03:04 install sshd[31490]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.213.122.26  user=backup
Sep 24 05:03:06 install sshd[31490]: Failed password for backup from 129.213.122.26 port 56294 ssh2
Sep 24 05:03:06 install sshd[31490]: Received disconnect from 129.213.122.26 port 56294:11: Bye Bye [preauth]
Sep 24 05:03:06 install sshd[31490]: Disconnected from authenticating user backup 129.213.122.26 port 56294 [preauth]
Sep 24 05:31:10 install sshd[4101]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.213.122.26  user=admin
Sep 24 05:31:11 install sshd[4101]: Failed password for admin from 129.213.122.26 port 52886 ssh2
Sep 24 05:31:11 install sshd[4101]: Received disconnect from 129.213.122.26 port 52886:11: Bye Bye [preauth]
Sep 24 05:31:11 install sshd[4101]: Disconnected from authenticating user admin 129.213.122.26 port 52........
------------------------------
2019-09-26 17:04:43
193.32.160.142 attack
$f2bV_matches
2019-09-26 17:00:06
106.75.17.91 attack
Sep 25 19:58:14 php1 sshd\[10217\]: Invalid user usuario from 106.75.17.91
Sep 25 19:58:14 php1 sshd\[10217\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.75.17.91
Sep 25 19:58:17 php1 sshd\[10217\]: Failed password for invalid user usuario from 106.75.17.91 port 55580 ssh2
Sep 25 20:03:38 php1 sshd\[10593\]: Invalid user carus from 106.75.17.91
Sep 25 20:03:38 php1 sshd\[10593\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.75.17.91
2019-09-26 17:18:53
49.148.189.139 attackbotsspam
Attempt to attack host OS, exploiting network vulnerabilities, on 26-09-2019 04:45:34.
2019-09-26 17:32:47
85.15.82.99 attackspambots
Attempt to attack host OS, exploiting network vulnerabilities, on 26-09-2019 04:45:34.
2019-09-26 17:31:09
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
171.22.148.17 attackbotsspam
Sep 25 06:24:00 mxgate1 postfix/postscreen[28403]: CONNECT from [171.22.148.17]:59049 to [176.31.12.44]:25
Sep 25 06:24:00 mxgate1 postfix/dnsblog[28538]: addr 171.22.148.17 listed by domain zen.spamhaus.org as 127.0.0.4
Sep 25 06:24:00 mxgate1 postfix/dnsblog[28538]: addr 171.22.148.17 listed by domain zen.spamhaus.org as 127.0.0.3
Sep 25 06:24:00 mxgate1 postfix/dnsblog[28536]: addr 171.22.148.17 listed by domain cbl.abuseat.org as 127.0.0.2
Sep 25 06:24:00 mxgate1 postfix/dnsblog[28537]: addr 171.22.148.17 listed by domain bl.spamcop.net as 127.0.0.2
Sep 25 06:24:01 mxgate1 postfix/postscreen[28403]: PREGREET 17 after 0.61 from [171.22.148.17]:59049: EHLO 009191.com

Sep 25 06:24:01 mxgate1 postfix/dnsblog[28784]: addr 171.22.148.17 listed by domain ix.dnsbl.xxxxxx.net as 127.0.0.2
Sep 25 06:24:07 mxgate1 postfix/postscreen[28403]: DNSBL rank 5 for [171.22.148.17]:59049
Sep x@x
Sep 25 06:24:11 mxgate1 postfix/postscreen[28403]: HANGUP after 3.9 from [171.22.148.17]:5........
-------------------------------
2019-09-26 17:20:37

Recently Reported IPs

157.50.240.52 92.63.196.7 189.8.108.73 172.110.73.170
2607:5300:60:139f::1 118.24.145.89 89.246.233.34 191.209.99.112
1.220.9.68 222.235.242.224 142.93.72.131 212.124.188.103
228.88.68.62 35.238.81.17 5.9.151.57 161.126.94.95
83.212.74.140 132.66.231.148 178.128.221.179 159.232.148.222