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

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

;; QUESTION SECTION:
;45.70.106.70.			IN	A

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

;; Query time: 19 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Jun 16 02:43:32 CST 2022
;; MSG SIZE  rcvd: 105
Host info
b'70.106.70.45.in-addr.arpa domain name pointer 45-70-106-70.customer.toplinetech.com.br.
'
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
70.106.70.45.in-addr.arpa	name = 45-70-106-70.customer.toplinetech.com.br.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
153.36.236.151 attackbots
Jul501:24:40server2sshd[10020]:refusedconnectfrom153.36.236.151\(153.36.236.151\)Jul501:24:41server2sshd[10033]:refusedconnectfrom153.36.236.151\(153.36.236.151\)Jul501:24:42server2sshd[10059]:refusedconnectfrom153.36.236.151\(153.36.236.151\)Jul501:24:45server2sshd[10089]:refusedconnectfrom153.36.236.151\(153.36.236.151\)Jul501:24:57server2sshd[10264]:refusedconnectfrom153.36.236.151\(153.36.236.151\)
2019-07-05 07:33:28
217.7.239.117 attack
Jul  5 01:45:41 core01 sshd\[27931\]: Invalid user ding from 217.7.239.117 port 57880
Jul  5 01:45:41 core01 sshd\[27931\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=217.7.239.117
...
2019-07-05 07:46:32
59.1.48.98 attack
Jul  5 00:59:12 tux-35-217 sshd\[3529\]: Invalid user glavbuh from 59.1.48.98 port 16542
Jul  5 00:59:12 tux-35-217 sshd\[3529\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=59.1.48.98
Jul  5 00:59:14 tux-35-217 sshd\[3529\]: Failed password for invalid user glavbuh from 59.1.48.98 port 16542 ssh2
Jul  5 01:01:49 tux-35-217 sshd\[3545\]: Invalid user mbrown from 59.1.48.98 port 29314
Jul  5 01:01:49 tux-35-217 sshd\[3545\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=59.1.48.98
...
2019-07-05 07:28:46
84.123.13.17 attackspambots
Jul  5 00:58:02 tuxlinux sshd[40132]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=84.123.13.17  user=root
Jul  5 00:58:04 tuxlinux sshd[40132]: Failed password for root from 84.123.13.17 port 50679 ssh2
Jul  5 00:58:02 tuxlinux sshd[40132]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=84.123.13.17  user=root
Jul  5 00:58:04 tuxlinux sshd[40132]: Failed password for root from 84.123.13.17 port 50679 ssh2
...
2019-07-05 07:50:52
211.138.182.198 attackbotsspam
$f2bV_matches
2019-07-05 07:52:55
198.108.67.55 attackbotsspam
Port scan: Attack repeated for 24 hours
2019-07-05 07:26:31
206.189.209.142 attackspambots
19/7/4@19:38:40: FAIL: Alarm-Intrusion address from=206.189.209.142
...
2019-07-05 07:51:27
178.62.37.78 attackspam
Jul  5 01:32:50 lnxweb62 sshd[4690]: Failed password for root from 178.62.37.78 port 59032 ssh2
Jul  5 01:32:50 lnxweb62 sshd[4690]: Failed password for root from 178.62.37.78 port 59032 ssh2
2019-07-05 07:45:58
23.97.70.232 attack
detected by Fail2Ban
2019-07-05 07:45:29
223.97.193.186 attackspambots
port scan and connect, tcp 23 (telnet)
2019-07-05 07:58:40
180.76.97.86 attack
Jul  4 18:15:18 mailman sshd[12068]: Invalid user joker from 180.76.97.86
Jul  4 18:15:18 mailman sshd[12068]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.76.97.86 
Jul  4 18:15:21 mailman sshd[12068]: Failed password for invalid user joker from 180.76.97.86 port 50214 ssh2
2019-07-05 07:59:34
202.93.8.37 attack
Unauthorised access (Jul  5) SRC=202.93.8.37 LEN=40 TTL=245 ID=47108 TCP DPT=445 WINDOW=1024 SYN 
Unauthorised access (Jul  4) SRC=202.93.8.37 LEN=40 TTL=245 ID=4618 TCP DPT=445 WINDOW=1024 SYN
2019-07-05 07:59:49
85.95.170.126 attackbots
[portscan] Port scan
2019-07-05 07:14:45
157.55.39.96 attack
Automatic report - Web App Attack
2019-07-05 07:12:05
222.175.125.66 attack
Jul  5 00:58:40 web1 sshd\[10269\]: Invalid user pi from 222.175.125.66
Jul  5 00:58:40 web1 sshd\[10271\]: Invalid user pi from 222.175.125.66
Jul  5 00:58:40 web1 sshd\[10269\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.175.125.66
Jul  5 00:58:40 web1 sshd\[10271\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.175.125.66
Jul  5 00:58:42 web1 sshd\[10269\]: Failed password for invalid user pi from 222.175.125.66 port 48582 ssh2
2019-07-05 07:31:34

Recently Reported IPs

45.70.94.133 137.226.248.235 45.57.160.134 45.163.173.30
23.236.198.114 35.190.190.33 38.132.233.101 131.100.137.183
49.85.97.114 49.85.98.241 49.85.97.249 49.85.98.184
49.85.99.47 49.85.99.170 49.85.111.29 49.85.99.228
49.85.162.44 45.32.153.249 78.48.47.180 45.12.30.166