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

;; QUESTION SECTION:
;30.214.23.138.			IN	A

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

;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 13 08:32:30 CST 2025
;; MSG SIZE  rcvd: 106
Host info
Host 138.23.214.30.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 138.23.214.30.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
202.191.200.227 attackbotsspam
[ssh] SSH attack
2019-12-07 21:06:23
206.189.93.108 attack
2019-12-07T02:58:24.356043suse-nuc sshd[19570]: Invalid user eslava from 206.189.93.108 port 40236
...
2019-12-07 21:29:06
103.100.209.174 attack
2019-12-07T10:28:06.394013centos sshd\[25640\]: Invalid user drivon from 103.100.209.174 port 16258
2019-12-07T10:28:06.400064centos sshd\[25640\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.100.209.174
2019-12-07T10:28:08.076897centos sshd\[25640\]: Failed password for invalid user drivon from 103.100.209.174 port 16258 ssh2
2019-12-07 21:20:10
36.189.253.226 attackspambots
2019-12-07T11:24:33.100601abusebot.cloudsearch.cf sshd\[27758\]: Invalid user cheung from 36.189.253.226 port 57262
2019-12-07 21:07:38
218.92.0.134 attackspam
Dec  7 14:24:55 eventyay sshd[889]: Failed password for root from 218.92.0.134 port 25643 ssh2
Dec  7 14:24:58 eventyay sshd[889]: Failed password for root from 218.92.0.134 port 25643 ssh2
Dec  7 14:25:08 eventyay sshd[889]: error: maximum authentication attempts exceeded for root from 218.92.0.134 port 25643 ssh2 [preauth]
...
2019-12-07 21:33:39
185.105.246.126 attackbots
Dec  7 13:18:01 ns382633 sshd\[4270\]: Invalid user hanken from 185.105.246.126 port 13137
Dec  7 13:18:01 ns382633 sshd\[4270\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.105.246.126
Dec  7 13:18:04 ns382633 sshd\[4270\]: Failed password for invalid user hanken from 185.105.246.126 port 13137 ssh2
Dec  7 13:23:47 ns382633 sshd\[5153\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.105.246.126  user=root
Dec  7 13:23:49 ns382633 sshd\[5153\]: Failed password for root from 185.105.246.126 port 7781 ssh2
2019-12-07 21:32:18
51.89.166.45 attackbotsspam
Dec  7 09:26:40 ns382633 sshd\[27768\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.89.166.45  user=root
Dec  7 09:26:42 ns382633 sshd\[27768\]: Failed password for root from 51.89.166.45 port 53100 ssh2
Dec  7 09:33:51 ns382633 sshd\[28856\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.89.166.45  user=root
Dec  7 09:33:53 ns382633 sshd\[28856\]: Failed password for root from 51.89.166.45 port 34864 ssh2
Dec  7 09:38:55 ns382633 sshd\[29638\]: Invalid user films from 51.89.166.45 port 44330
Dec  7 09:38:55 ns382633 sshd\[29638\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.89.166.45
2019-12-07 21:50:30
69.162.108.70 attackspam
69.162.108.70 was recorded 6 times by 5 hosts attempting to connect to the following ports: 5060. Incident counter (4h, 24h, all-time): 6, 8, 54
2019-12-07 21:07:07
216.99.112.252 attackspambots
Host Scan
2019-12-07 21:51:41
122.51.23.52 attackspam
Brute-force attempt banned
2019-12-07 21:19:20
223.204.97.124 attack
Port 1433 Scan
2019-12-07 21:09:02
108.223.130.246 attack
Dec707:23:39server4pure-ftpd:\(\?@1.28.206.105\)[WARNING]Authenticationfailedforuser[www]Dec707:24:35server4pure-ftpd:\(\?@108.223.130.246\)[WARNING]Authenticationfailedforuser[www]Dec707:24:24server4pure-ftpd:\(\?@108.223.130.246\)[WARNING]Authenticationfailedforuser[www]Dec707:24:24server4pure-ftpd:\(\?@108.223.130.246\)[WARNING]Authenticationfailedforuser[www]Dec707:23:53server4pure-ftpd:\(\?@1.28.206.105\)[WARNING]Authenticationfailedforuser[www]Dec707:23:54server4pure-ftpd:\(\?@108.223.130.246\)[WARNING]Authenticationfailedforuser[www]Dec707:24:19server4pure-ftpd:\(\?@1.28.206.105\)[WARNING]Authenticationfailedforuser[www]Dec707:24:28server4pure-ftpd:\(\?@1.28.206.105\)[WARNING]Authenticationfailedforuser[www]Dec707:24:00server4pure-ftpd:\(\?@1.28.206.105\)[WARNING]Authenticationfailedforuser[www]Dec707:23:23server4pure-ftpd:\(\?@1.28.206.105\)[WARNING]Authenticationfailedforuser[www]IPAddressesBlocked:1.28.206.105\(CN/China/-\)
2019-12-07 21:43:53
211.47.91.124 attack
UTC: 2019-12-06 port: 123/udp
2019-12-07 21:14:14
187.45.116.52 attack
UTC: 2019-12-06 port: 23/tcp
2019-12-07 21:22:16
185.53.88.4 attack
185.53.88.4 was recorded 9 times by 9 hosts attempting to connect to the following ports: 5060. Incident counter (4h, 24h, all-time): 9, 14, 552
2019-12-07 21:11:33

Recently Reported IPs

53.100.139.66 231.15.88.243 224.155.64.202 144.138.2.14
152.158.175.64 232.163.135.193 153.209.171.222 9.116.52.75
95.85.79.20 45.130.6.106 237.5.2.240 127.208.254.200
190.68.124.191 156.72.155.77 60.86.211.237 226.62.33.157
145.178.92.29 217.142.235.52 41.237.171.106 13.195.162.65