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

;; QUESTION SECTION:
;70.19.218.68.			IN	A

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

;; Query time: 38 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 17 23:01:27 CST 2025
;; MSG SIZE  rcvd: 105
Host info
68.218.19.70.in-addr.arpa domain name pointer pool-70-19-218-68.bos.east.verizon.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
68.218.19.70.in-addr.arpa	name = pool-70-19-218-68.bos.east.verizon.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
222.186.52.189 attackbots
Unauthorized connection attempt detected from IP address 222.186.52.189 to port 22 [J]
2020-01-13 13:37:12
128.199.232.214 attack
Bad crawling causing excessive 404 errors
2020-01-13 13:25:47
201.211.168.240 attack
Unauthorized connection attempt detected from IP address 201.211.168.240 to port 1433 [J]
2020-01-13 13:29:45
123.207.153.52 attackbots
Jan 13 05:53:54 lnxded63 sshd[30478]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.207.153.52
2020-01-13 13:18:59
82.117.168.78 attack
1578891229 - 01/13/2020 05:53:49 Host: 82.117.168.78/82.117.168.78 Port: 445 TCP Blocked
2020-01-13 13:23:55
222.186.169.194 attackbotsspam
Jan 13 06:04:57 dcd-gentoo sshd[13434]: User root from 222.186.169.194 not allowed because none of user's groups are listed in AllowGroups
Jan 13 06:04:59 dcd-gentoo sshd[13434]: error: PAM: Authentication failure for illegal user root from 222.186.169.194
Jan 13 06:04:57 dcd-gentoo sshd[13434]: User root from 222.186.169.194 not allowed because none of user's groups are listed in AllowGroups
Jan 13 06:04:59 dcd-gentoo sshd[13434]: error: PAM: Authentication failure for illegal user root from 222.186.169.194
Jan 13 06:04:57 dcd-gentoo sshd[13434]: User root from 222.186.169.194 not allowed because none of user's groups are listed in AllowGroups
Jan 13 06:04:59 dcd-gentoo sshd[13434]: error: PAM: Authentication failure for illegal user root from 222.186.169.194
Jan 13 06:04:59 dcd-gentoo sshd[13434]: Failed keyboard-interactive/pam for invalid user root from 222.186.169.194 port 45814 ssh2
...
2020-01-13 13:17:13
49.88.112.61 attackspam
Jan 13 06:22:30 silence02 sshd[16723]: Failed password for root from 49.88.112.61 port 26693 ssh2
Jan 13 06:22:40 silence02 sshd[16723]: Failed password for root from 49.88.112.61 port 26693 ssh2
Jan 13 06:22:43 silence02 sshd[16723]: Failed password for root from 49.88.112.61 port 26693 ssh2
Jan 13 06:22:43 silence02 sshd[16723]: error: maximum authentication attempts exceeded for root from 49.88.112.61 port 26693 ssh2 [preauth]
2020-01-13 13:29:28
104.229.203.202 attackspambots
2020-01-13T04:52:02.634056shield sshd\[29986\]: Invalid user weblogic from 104.229.203.202 port 45422
2020-01-13T04:52:02.637944shield sshd\[29986\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=cpe-104-229-203-202.twcny.res.rr.com
2020-01-13T04:52:04.667461shield sshd\[29986\]: Failed password for invalid user weblogic from 104.229.203.202 port 45422 ssh2
2020-01-13T04:53:54.935598shield sshd\[30465\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=cpe-104-229-203-202.twcny.res.rr.com  user=root
2020-01-13T04:53:56.334475shield sshd\[30465\]: Failed password for root from 104.229.203.202 port 35008 ssh2
2020-01-13 13:16:28
80.82.77.86 attackbotsspam
80.82.77.86 was recorded 237 times by 1 hosts attempting to connect to the following ports: 69. Incident counter (4h, 24h, all-time): 237, 742, 5042
2020-01-13 13:10:52
134.209.56.217 attack
Portscan or hack attempt detected by psad/fwsnort
2020-01-13 13:47:34
96.237.162.65 attack
Honeypot attack, port: 81, PTR: pool-96-237-162-65.bstnma.fios.verizon.net.
2020-01-13 13:38:55
163.172.61.214 attack
Unauthorized connection attempt detected from IP address 163.172.61.214 to port 2220 [J]
2020-01-13 13:43:44
187.167.193.119 attack
Honeypot attack, port: 445, PTR: 187-167-193-119.static.axtel.net.
2020-01-13 13:44:19
220.133.1.121 attackbotsspam
Honeypot attack, port: 81, PTR: 220-133-1-121.HINET-IP.hinet.net.
2020-01-13 13:15:44
106.13.168.150 attackbotsspam
Jan 13 05:53:23 lnxded63 sshd[30444]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.168.150
2020-01-13 13:45:10

Recently Reported IPs

177.37.105.162 24.60.52.73 170.238.34.13 32.238.98.217
125.233.125.190 221.70.104.241 142.204.72.151 97.79.150.215
170.58.132.57 252.34.16.69 211.215.206.3 51.38.168.140
233.250.28.22 230.167.157.84 253.147.93.34 67.35.229.198
132.211.177.38 28.249.192.252 145.172.37.163 215.221.157.53