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

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

;; QUESTION SECTION:
;104.105.34.230.			IN	A

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

;; Query time: 63 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Mar 05 01:10:57 CST 2022
;; MSG SIZE  rcvd: 107
Host info
230.34.105.104.in-addr.arpa domain name pointer a104-105-34-230.deploy.static.akamaitechnologies.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
230.34.105.104.in-addr.arpa	name = a104-105-34-230.deploy.static.akamaitechnologies.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
185.101.105.194 attack
19/10/7@07:39:17: FAIL: IoT-Telnet address from=185.101.105.194
19/10/7@07:39:17: FAIL: IoT-Telnet address from=185.101.105.194
19/10/7@07:39:17: FAIL: IoT-Telnet address from=185.101.105.194
...
2019-10-08 01:53:45
106.12.132.81 attack
Oct  7 14:28:29 localhost sshd\[13753\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.132.81  user=root
Oct  7 14:28:30 localhost sshd\[13753\]: Failed password for root from 106.12.132.81 port 45461 ssh2
Oct  7 14:32:20 localhost sshd\[14254\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.132.81  user=root
2019-10-08 01:28:33
118.121.201.83 attackbotsspam
Oct  7 18:48:15 lcl-usvr-01 sshd[1538]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.121.201.83  user=root
Oct  7 18:53:22 lcl-usvr-01 sshd[3098]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.121.201.83  user=root
Oct  7 18:58:14 lcl-usvr-01 sshd[4623]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.121.201.83  user=root
2019-10-08 01:41:30
119.90.89.90 attack
Automatic report - SSH Brute-Force Attack
2019-10-08 01:52:42
149.202.45.205 attack
2019-10-07T11:39:10.547303abusebot-5.cloudsearch.cf sshd\[21313\]: Invalid user Www@2018 from 149.202.45.205 port 60864
2019-10-08 01:58:02
37.143.130.124 attackspam
CloudCIX Reconnaissance Scan Detected, PTR: PTR record not found
2019-10-08 01:21:57
89.222.181.58 attackbots
Oct  7 19:23:29 ns381471 sshd[31007]: Failed password for root from 89.222.181.58 port 59876 ssh2
Oct  7 19:27:56 ns381471 sshd[31152]: Failed password for root from 89.222.181.58 port 43416 ssh2
2019-10-08 01:33:43
107.189.2.139 attack
WordPress wp-login brute force :: 107.189.2.139 0.116 BYPASS [07/Oct/2019:22:40:19  1100] [censored_1] "POST /wp-login.php HTTP/1.1" 200 3972 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
2019-10-08 01:28:10
103.133.107.130 attackbotsspam
Oct  7 07:40:17 123flo sshd[5851]: Invalid user support from 103.133.107.130
Oct  7 07:40:17 123flo sshd[5851]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.133.107.130 
Oct  7 07:40:17 123flo sshd[5851]: Invalid user support from 103.133.107.130
Oct  7 07:40:19 123flo sshd[5851]: Failed password for invalid user support from 103.133.107.130 port 51652 ssh2
Oct  7 07:40:20 123flo sshd[5855]: Invalid user admin from 103.133.107.130
2019-10-08 01:27:15
193.31.210.42 attack
Port scan
2019-10-08 01:39:45
185.209.0.92 attackbotsspam
10/07/2019-18:44:10.342590 185.209.0.92 Protocol: 6 ET DROP Dshield Block Listed Source group 1
2019-10-08 01:21:05
51.68.126.243 attack
Oct  7 17:59:25 markkoudstaal sshd[2606]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.68.126.243
Oct  7 17:59:26 markkoudstaal sshd[2606]: Failed password for invalid user T3ST123!@# from 51.68.126.243 port 40032 ssh2
Oct  7 18:03:33 markkoudstaal sshd[2970]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.68.126.243
2019-10-08 01:36:49
80.211.116.102 attackspam
Oct  7 13:04:51 unicornsoft sshd\[23567\]: User root from 80.211.116.102 not allowed because not listed in AllowUsers
Oct  7 13:04:51 unicornsoft sshd\[23567\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.211.116.102  user=root
Oct  7 13:04:53 unicornsoft sshd\[23567\]: Failed password for invalid user root from 80.211.116.102 port 54003 ssh2
2019-10-08 01:48:03
141.98.10.60 attack
Oct  7 17:16:36 mail postfix/smtpd\[26237\]: warning: unknown\[141.98.10.60\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\
Oct  7 17:42:04 mail postfix/smtpd\[27657\]: warning: unknown\[141.98.10.60\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\
Oct  7 18:32:51 mail postfix/smtpd\[29624\]: warning: unknown\[141.98.10.60\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\
Oct  7 18:58:12 mail postfix/smtpd\[30191\]: warning: unknown\[141.98.10.60\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\
2019-10-08 01:57:04
106.13.175.210 attackbotsspam
Oct  7 19:01:26 vps647732 sshd[7960]: Failed password for root from 106.13.175.210 port 58780 ssh2
...
2019-10-08 01:18:50

Recently Reported IPs

104.102.138.111 114.24.40.102 104.105.36.112 104.105.36.225
104.105.43.152 104.105.33.79 104.105.80.104 104.105.81.5
104.105.84.180 104.105.80.156 104.102.133.5 104.105.82.11
104.105.40.246 104.105.89.210 104.105.89.169 104.105.86.133
104.105.90.60 104.105.89.238 114.24.40.106 104.105.92.188