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

;; QUESTION SECTION:
;108.157.162.18.			IN	A

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

;; Query time: 100 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Apr 09 04:29:17 CST 2022
;; MSG SIZE  rcvd: 107
Host info
18.162.157.108.in-addr.arpa domain name pointer server-108-157-162-18.mia3.r.cloudfront.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
18.162.157.108.in-addr.arpa	name = server-108-157-162-18.mia3.r.cloudfront.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
123.207.98.11 attackbots
Dec 17 22:58:58 auw2 sshd\[30201\]: Invalid user lagarde from 123.207.98.11
Dec 17 22:58:58 auw2 sshd\[30201\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.207.98.11
Dec 17 22:58:59 auw2 sshd\[30201\]: Failed password for invalid user lagarde from 123.207.98.11 port 33462 ssh2
Dec 17 23:04:24 auw2 sshd\[30707\]: Invalid user thibert from 123.207.98.11
Dec 17 23:04:24 auw2 sshd\[30707\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.207.98.11
2019-12-18 21:45:56
139.59.41.154 attackspam
$f2bV_matches
2019-12-18 22:14:11
103.141.234.19 attack
103.141.234.19 - - \[18/Dec/2019:07:59:06 +0100\] "POST /wp-login.php HTTP/1.0" 200 6640 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
103.141.234.19 - - \[18/Dec/2019:07:59:09 +0100\] "POST /wp-login.php HTTP/1.0" 200 6453 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
103.141.234.19 - - \[18/Dec/2019:07:59:12 +0100\] "POST /wp-login.php HTTP/1.0" 200 6453 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
2019-12-18 22:11:51
103.134.133.50 attackbotsspam
Honeypot attack, port: 23, PTR: PTR record not found
2019-12-18 22:10:07
178.68.192.242 attackspam
Unauthorized connection attempt detected from IP address 178.68.192.242 to port 445
2019-12-18 21:50:08
139.159.27.62 attackbotsspam
Dec 18 07:43:10 vmd17057 sshd\[20942\]: Invalid user schaul from 139.159.27.62 port 54714
Dec 18 07:43:10 vmd17057 sshd\[20942\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.159.27.62
Dec 18 07:43:12 vmd17057 sshd\[20942\]: Failed password for invalid user schaul from 139.159.27.62 port 54714 ssh2
...
2019-12-18 22:01:17
210.177.54.141 attack
2019-12-18T10:59:25.728325abusebot-5.cloudsearch.cf sshd\[25467\]: Invalid user gdm from 210.177.54.141 port 48368
2019-12-18T10:59:25.733503abusebot-5.cloudsearch.cf sshd\[25467\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.177.54.141
2019-12-18T10:59:27.950106abusebot-5.cloudsearch.cf sshd\[25467\]: Failed password for invalid user gdm from 210.177.54.141 port 48368 ssh2
2019-12-18T11:08:02.760661abusebot-5.cloudsearch.cf sshd\[25564\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.177.54.141  user=root
2019-12-18 22:22:04
40.92.11.59 attackspambots
Dec 18 09:24:25 debian-2gb-vpn-nbg1-1 kernel: [1028630.744184] [UFW BLOCK] IN=eth0 OUT= MAC=96:00:00:38:96:44:d2:74:7f:6e:37:e3:08:00 SRC=40.92.11.59 DST=78.46.192.101 LEN=40 TOS=0x00 PREC=0x00 TTL=231 ID=57786 DF PROTO=TCP SPT=48924 DPT=25 WINDOW=0 RES=0x00 ACK RST URGP=0
2019-12-18 21:49:41
103.25.0.202 attackspambots
103.25.0.202 has been banned for [spam]
...
2019-12-18 22:02:48
182.74.157.242 attackspam
Automatic report - Port Scan Attack
2019-12-18 22:18:48
61.7.235.211 attackbotsspam
Invalid user service from 61.7.235.211 port 34534
2019-12-18 22:15:37
1.203.115.140 attackspambots
SSH invalid-user multiple login attempts
2019-12-18 22:12:14
14.63.221.108 attackspambots
SSH Brute Force
2019-12-18 21:55:13
216.218.206.113 attackspambots
216.218.206.113 was recorded 5 times by 5 hosts attempting to connect to the following ports: 30005,1434. Incident counter (4h, 24h, all-time): 5, 8, 191
2019-12-18 22:05:00
110.138.150.139 attackbotsspam
Unauthorized connection attempt detected from IP address 110.138.150.139 to port 445
2019-12-18 21:54:45

Recently Reported IPs

108.156.91.91 108.157.162.56 108.157.214.112 108.157.214.121
108.157.214.16 108.157.214.38 108.157.214.85 108.157.4.110
108.157.4.118 108.157.4.121 108.157.4.25 108.157.4.31
109.118.100.207 109.118.102.35 109.118.127.179 109.12.25.203
109.120.166.37 109.122.193.251 109.123.101.72 109.123.119.202