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: Kazakhstan

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

;; QUESTION SECTION:
;45.10.234.5.			IN	A

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

;; Query time: 45 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun May 01 06:45:59 CST 2022
;; MSG SIZE  rcvd: 104
Host info
Host 5.234.10.45.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 5.234.10.45.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
23.80.97.223 attack
(From wordpresswizardwes@yahoo.com) Hi there,

I came across your website yesterday and ran into some missed opportunities I think you’ll want to take a look at!

I own a digital marketing company in Kingston Ontario, and can already see several minor improvements that would be solved by a basic website management package. Although cheap, this can significantly improve your online presence and outreach.

I know you’re probably very busy, but if you would like to learn more I'd be happy to send you a link with all the details.

I look forward to your response,

Wes
2020-04-02 04:49:46
138.68.82.194 attackbots
[ssh] SSH attack
2020-04-02 05:01:36
176.109.191.228 attackbotsspam
" "
2020-04-02 04:40:51
109.102.129.67 attackspam
Port 23 (Telnet) access denied
2020-04-02 04:50:37
176.31.182.79 attackbotsspam
Apr  1 22:00:04  sshd\[20969\]: User root from ns3326271.ip-176-31-182.eu not allowed because not listed in AllowUsersApr  1 22:00:06  sshd\[20969\]: Failed password for invalid user root from 176.31.182.79 port 56566 ssh2
...
2020-04-02 04:45:24
106.12.106.42 attackbots
Unauthorized SSH login attempts
2020-04-02 05:01:57
185.219.221.154 attack
04/01/2020-08:27:09.229658 185.219.221.154 Protocol: 17 GPL EXPLOIT ntpdx overflow attempt
2020-04-02 04:56:51
80.211.136.164 attackspam
Port 940 scan denied
2020-04-02 04:59:30
49.234.44.48 attack
Apr  1 22:38:27 ewelt sshd[3283]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.44.48
Apr  1 22:38:27 ewelt sshd[3283]: Invalid user ze from 49.234.44.48 port 48659
Apr  1 22:38:30 ewelt sshd[3283]: Failed password for invalid user ze from 49.234.44.48 port 48659 ssh2
Apr  1 22:43:24 ewelt sshd[3651]: Invalid user alarm from 49.234.44.48 port 50565
...
2020-04-02 04:47:06
51.15.252.216 attackbots
Apr  1 22:15:57 vpn01 sshd[1357]: Failed password for root from 51.15.252.216 port 36498 ssh2
...
2020-04-02 05:04:13
5.189.139.206 attackspambots
Telnet/23 MH Probe, Scan, BF, Hack -
2020-04-02 04:50:13
222.186.30.218 attackbotsspam
DATE:2020-04-01 22:54:18, IP:222.186.30.218, PORT:ssh SSH brute force auth on honeypot server (epe-honey1-hq)
2020-04-02 04:55:28
106.12.12.242 attackspam
Apr  1 14:02:42 ns382633 sshd\[10646\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.12.242  user=root
Apr  1 14:02:43 ns382633 sshd\[10646\]: Failed password for root from 106.12.12.242 port 33415 ssh2
Apr  1 14:17:05 ns382633 sshd\[13803\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.12.242  user=root
Apr  1 14:17:07 ns382633 sshd\[13803\]: Failed password for root from 106.12.12.242 port 44109 ssh2
Apr  1 14:27:44 ns382633 sshd\[15847\]: Invalid user ypz from 106.12.12.242 port 44138
Apr  1 14:27:44 ns382633 sshd\[15847\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.12.242
2020-04-02 04:32:30
173.252.87.45 attackbotsspam
[Wed Apr 01 19:51:15.867889 2020] [:error] [pid 13155:tid 140357682616064] [client 173.252.87.45:63876] [client 173.252.87.45] ModSecurity: Access denied with code 403 (phase 2). Match of "eq 0" against "&REQUEST_HEADERS:Transfer-Encoding" required. [file "/etc/modsecurity/owasp-modsecurity-crs-3.2.0/rules/REQUEST-920-PROTOCOL-ENFORCEMENT.conf"] [line "202"] [id "920171"] [msg "GET or HEAD Request with Transfer-Encoding."] [data "1"] [severity "CRITICAL"] [ver "OWASP_CRS/3.2.0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-protocol"] [tag "OWASP_CRS"] [tag "OWASP_CRS/PROTOCOL_VIOLATION/INVALID_HREQ"] [tag "CAPEC-272"] [hostname "karangploso.jatim.bmkg.go.id"] [uri "/favicon-32-32.png"] [unique_id "XoSOQ-EBhu3WEjTmXz-VmAAAAAE"]
...
2020-04-02 04:38:25
206.189.71.79 attackbots
Apr  1 18:41:20 sshgateway sshd\[23844\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.71.79  user=root
Apr  1 18:41:23 sshgateway sshd\[23844\]: Failed password for root from 206.189.71.79 port 44922 ssh2
Apr  1 18:45:12 sshgateway sshd\[23870\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.71.79  user=root
2020-04-02 04:29:26

Recently Reported IPs

126.169.240.10 125.167.182.90 222.188.21.35 10.171.4.213
192.168.38.237 188.20.214.236 159.79.78.169 45.140.55.156
177.86.115.155 128.27.76.88 167.86.115.155 92.192.38.255
66.212.8.50 251.65.201.111 18.29.79.114 15.111.230.32
154.242.75.140 154.85.204.12 193.44.71.79 252.160.159.122