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 of America (the)

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

;; QUESTION SECTION:
;70.99.63.161.			IN	A

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

;; Query time: 37 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Jan 23 21:12:26 CST 2025
;; MSG SIZE  rcvd: 105
Host info
161.63.99.70.in-addr.arpa has no PTR record
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
*** Can't find 161.63.99.70.in-addr.arpa.: No answer

Authoritative answers can be found from:
63.99.70.in-addr.arpa	nameserver = ns.eli.net.
63.99.70.in-addr.arpa	nameserver = ns2.eli.net.
Related IP info:
Related comments:
IP Type Details Datetime
196.202.120.18 attackbots
3389BruteforceFW21
2019-11-27 01:24:26
202.160.39.153 attackbotsspam
Unauthorized SMTP/IMAP/POP3 connection attempt
2019-11-27 01:21:27
110.34.28.99 attack
Unauthorised access (Nov 26) SRC=110.34.28.99 LEN=40 PREC=0x20 TTL=240 ID=18407 DF TCP DPT=23 WINDOW=14600 SYN
2019-11-27 01:34:57
180.101.221.152 attackbotsspam
Nov 26 13:16:52 server sshd\[16030\]: Failed password for invalid user home from 180.101.221.152 port 52206 ssh2
Nov 26 19:23:18 server sshd\[8399\]: Invalid user titi from 180.101.221.152
Nov 26 19:23:18 server sshd\[8399\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.101.221.152 
Nov 26 19:23:20 server sshd\[8399\]: Failed password for invalid user titi from 180.101.221.152 port 49924 ssh2
Nov 26 19:31:07 server sshd\[10469\]: Invalid user rompelman from 180.101.221.152
...
2019-11-27 01:07:49
202.164.213.50 attackbotsspam
IP Ban Report :  
 https://help-dysk.pl/wordpress-firewall-plugins/ip/202.164.213.50/ 
 
 BD - 1H : (8)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : BD 
 NAME ASN : ASN38026 
 
 IP : 202.164.213.50 
 
 CIDR : 202.164.213.0/24 
 
 PREFIX COUNT : 33 
 
 UNIQUE IP COUNT : 9216 
 
 
 ATTACKS DETECTED ASN38026 :  
  1H - 1 
  3H - 1 
  6H - 1 
 12H - 1 
 24H - 1 
 
 DateTime : 2019-11-26 15:44:29 
 
 INFO :  HACK ! - Looking for resource vulnerabilities Scan Detected and Blocked by ADMIN  - data recovery
2019-11-27 01:36:28
222.186.175.182 attackspambots
Nov 26 18:31:28 vpn01 sshd[2019]: Failed password for root from 222.186.175.182 port 44688 ssh2
Nov 26 18:31:30 vpn01 sshd[2019]: Failed password for root from 222.186.175.182 port 44688 ssh2
...
2019-11-27 01:31:53
139.215.143.20 attackspam
Nov 26 18:11:29 eventyay sshd[25111]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.215.143.20
Nov 26 18:11:31 eventyay sshd[25111]: Failed password for invalid user lappin from 139.215.143.20 port 5384 ssh2
Nov 26 18:16:24 eventyay sshd[25183]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.215.143.20
...
2019-11-27 01:28:22
35.170.159.42 attack
RDP Bruteforce
2019-11-27 01:34:02
52.35.136.194 attackspam
11/26/2019-18:16:02.795981 52.35.136.194 Protocol: 6 SURICATA TLS invalid record/traffic
2019-11-27 01:16:11
183.80.176.200 attack
Unauthorised access (Nov 26) SRC=183.80.176.200 LEN=40 TTL=47 ID=45210 TCP DPT=23 WINDOW=38249 SYN 
Unauthorised access (Nov 26) SRC=183.80.176.200 LEN=40 TTL=47 ID=45210 TCP DPT=23 WINDOW=38249 SYN 
Unauthorised access (Nov 26) SRC=183.80.176.200 LEN=40 TTL=47 ID=45210 TCP DPT=23 WINDOW=38249 SYN 
Unauthorised access (Nov 26) SRC=183.80.176.200 LEN=40 TTL=47 ID=45210 TCP DPT=23 WINDOW=38249 SYN
2019-11-27 01:33:09
1.0.212.35 attackbots
19/11/26@09:44:39: FAIL: IoT-Telnet address from=1.0.212.35
...
2019-11-27 01:30:26
171.251.36.189 attackbots
Automatic report - Port Scan Attack
2019-11-27 01:08:27
175.204.91.168 attackspam
2019-11-26T17:57:37.514762tmaserv sshd\[5577\]: Failed password for root from 175.204.91.168 port 43366 ssh2
2019-11-26T18:57:40.426349tmaserv sshd\[8381\]: Invalid user squid from 175.204.91.168 port 45798
2019-11-26T18:57:40.431262tmaserv sshd\[8381\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.204.91.168
2019-11-26T18:57:42.466755tmaserv sshd\[8381\]: Failed password for invalid user squid from 175.204.91.168 port 45798 ssh2
2019-11-26T19:04:53.181769tmaserv sshd\[8712\]: Invalid user dieplinger from 175.204.91.168 port 53148
2019-11-26T19:04:53.190611tmaserv sshd\[8712\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.204.91.168
...
2019-11-27 01:28:56
119.29.114.235 attackbots
(sshd) Failed SSH login from 119.29.114.235 (-): 5 in the last 3600 secs
2019-11-27 01:40:03
106.12.47.203 attackspam
DATE:2019-11-26 15:55:05,IP:106.12.47.203,MATCHES:10,PORT:ssh
2019-11-27 01:41:55

Recently Reported IPs

13.178.189.61 9.94.201.47 145.21.56.126 86.81.239.150
165.90.94.25 13.56.51.137 25.250.18.184 122.190.196.110
161.147.58.19 162.240.136.94 78.226.13.65 254.99.178.255
81.94.41.98 217.22.77.47 191.57.192.251 128.201.24.89
200.2.90.105 132.167.237.110 54.65.188.95 213.172.149.238