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

;; QUESTION SECTION:
;70.221.139.142.			IN	A

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

;; Query time: 15 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 18 19:59:04 CST 2025
;; MSG SIZE  rcvd: 107
Host info
142.139.221.70.in-addr.arpa domain name pointer 142.sub-70-221-139.myvzw.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
142.139.221.70.in-addr.arpa	name = 142.sub-70-221-139.myvzw.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
14.215.116.6 attackspambots
Automatic report - Banned IP Access
2020-07-19 21:10:07
167.172.184.220 attack
Connection to SSH Honeypot - Detected by HoneypotDB
2020-07-19 21:13:02
129.226.73.26 attackbotsspam
Jul 19 15:03:01 OPSO sshd\[26273\]: Invalid user team2 from 129.226.73.26 port 40666
Jul 19 15:03:01 OPSO sshd\[26273\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.226.73.26
Jul 19 15:03:03 OPSO sshd\[26273\]: Failed password for invalid user team2 from 129.226.73.26 port 40666 ssh2
Jul 19 15:09:29 OPSO sshd\[27845\]: Invalid user pam from 129.226.73.26 port 55232
Jul 19 15:09:29 OPSO sshd\[27845\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.226.73.26
2020-07-19 21:22:05
171.67.71.100 attackbotsspam
47808/tcp 5672/tcp 13905/tcp...
[2020-06-04/07-11]584pkt,149pt.(tcp)
2020-07-19 20:51:44
198.46.209.148 attackbotsspam
Jul 19 14:58:58 debian-2gb-nbg1-2 kernel: \[17422083.297054\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=198.46.209.148 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=241 ID=54321 PROTO=TCP SPT=42617 DPT=8088 WINDOW=65535 RES=0x00 SYN URGP=0
2020-07-19 21:28:16
114.67.110.227 attack
odoo8
...
2020-07-19 20:51:59
51.68.123.192 attackbotsspam
$f2bV_matches
2020-07-19 21:07:36
101.75.157.16 attack
Port probing on unauthorized port 23
2020-07-19 21:20:26
193.228.91.11 attackbots
(sshd) Failed SSH login from 193.228.91.11 (GB/United Kingdom/-): 10 in the last 3600 secs
2020-07-19 21:30:25
218.92.0.219 attackspambots
Jul 19 14:57:27 home sshd[13698]: Failed password for root from 218.92.0.219 port 56805 ssh2
Jul 19 14:57:38 home sshd[13708]: Failed password for root from 218.92.0.219 port 24475 ssh2
...
2020-07-19 21:11:17
122.116.189.218 attackbots
port scan and connect, tcp 80 (http)
2020-07-19 21:10:30
120.220.242.30 attackspam
reported through recidive - multiple failed attempts(SSH)
2020-07-19 20:56:08
83.97.20.35 attackbots
 TCP (SYN) 83.97.20.35:60817 -> port 8443, len 44
2020-07-19 21:02:59
192.3.139.56 attack
[Sun Jul 05 05:26:24 2020] - DDoS Attack From IP: 192.3.139.56 Port: 51229
2020-07-19 21:09:14
119.45.0.9 attackspam
Invalid user zcy from 119.45.0.9 port 58692
2020-07-19 21:14:19

Recently Reported IPs

68.187.201.14 209.10.136.142 231.96.118.64 253.41.4.248
45.255.55.147 156.160.78.76 213.11.51.219 200.211.66.89
135.100.5.178 225.156.91.93 222.26.210.227 123.22.241.39
106.20.182.68 23.221.131.202 34.201.60.250 160.136.182.151
203.187.167.125 93.100.224.199 206.46.151.247 221.193.243.80