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

Region: Ohio

Country: United States

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

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;149.55.28.70.			IN	A

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

;; Query time: 71 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Sep 11 07:58:11 CST 2020
;; MSG SIZE  rcvd: 116
Host info
Host 70.28.55.149.in-addr.arpa not found: 2(SERVFAIL)
Nslookup info:
;; Got SERVFAIL reply from 100.100.2.138, trying next server
;; Got SERVFAIL reply from 100.100.2.136, trying next server
Server:		100.100.2.138
Address:	100.100.2.138#53

** server can't find 70.28.55.149.in-addr.arpa: SERVFAIL

Related IP info:
Related comments:
IP Type Details Datetime
92.40.22.18 attack
spying on anyone is illegal, for 15yrs even worse, tampered build to feed their racism -deal with the racism alb -tampering with ethnic minorities building even worse, brings everyone involved severe consequences - legally -well worth the wait, don't communicate with known racists 2007/2nd legal team involving the neighbour -review web workers/admins -city name usually name association/mountain view from ord muir of ord hackers/usually are tech/IT/dev/etc
2020-02-13 05:43:02
159.89.194.160 attackbots
Feb 12 22:10:03 legacy sshd[26307]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.89.194.160
Feb 12 22:10:05 legacy sshd[26307]: Failed password for invalid user jh from 159.89.194.160 port 46338 ssh2
Feb 12 22:13:14 legacy sshd[26582]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.89.194.160
...
2020-02-13 05:27:50
185.220.102.8 attackspam
Feb 12 08:27:45 web1 sshd\[24625\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.220.102.8  user=root
Feb 12 08:27:47 web1 sshd\[24625\]: Failed password for root from 185.220.102.8 port 36037 ssh2
Feb 12 08:29:37 web1 sshd\[24820\]: Invalid user pi from 185.220.102.8
Feb 12 08:29:38 web1 sshd\[24820\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.220.102.8
Feb 12 08:29:39 web1 sshd\[24820\]: Failed password for invalid user pi from 185.220.102.8 port 44893 ssh2
2020-02-13 05:56:18
121.121.105.54 attack
Telnetd brute force attack detected by fail2ban
2020-02-13 05:46:34
116.118.60.59 attackbotsspam
23/tcp
[2020-02-12]1pkt
2020-02-13 05:43:17
176.197.234.82 attackbots
23/tcp
[2020-02-12]1pkt
2020-02-13 05:42:42
77.40.2.103 attackbots
2020-02-12 14:39:35 auth_login authenticator failed for (localhost.localdomain) [77.40.2.103]: 535 Incorrect authentication data (set_id=admin@mhasc.org)
2020-02-12 14:39:35 auth_login authenticator failed for (localhost.localdomain) [77.40.2.103]: 535 Incorrect authentication data (set_id=administrator@mhasc.org)
...
2020-02-13 05:29:57
220.201.185.215 attackspambots
37215/tcp 37215/tcp
[2020-02-10/11]2pkt
2020-02-13 05:21:00
103.94.6.69 attackbots
Feb 12 17:25:14 pi sshd[14812]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.94.6.69 
Feb 12 17:25:16 pi sshd[14812]: Failed password for invalid user cxh from 103.94.6.69 port 39197 ssh2
2020-02-13 05:18:17
45.56.126.141 attackspam
Total attacks: 3
2020-02-13 05:33:51
109.194.14.231 attackbotsspam
Unauthorised access (Feb 12) SRC=109.194.14.231 LEN=40 TOS=0x10 PREC=0x60 TTL=54 ID=5426 TCP DPT=23 WINDOW=10433 SYN
2020-02-13 05:39:41
117.3.203.113 attackbots
Fail2Ban Ban Triggered
2020-02-13 05:48:14
77.29.164.60 attack
Automatic report - Port Scan Attack
2020-02-13 05:50:20
101.91.200.186 attackspambots
Feb 12 04:02:11 auw2 sshd\[24978\]: Invalid user postgres from 101.91.200.186
Feb 12 04:02:11 auw2 sshd\[24978\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.91.200.186
Feb 12 04:02:13 auw2 sshd\[24978\]: Failed password for invalid user postgres from 101.91.200.186 port 34768 ssh2
Feb 12 04:03:24 auw2 sshd\[25089\]: Invalid user duo from 101.91.200.186
Feb 12 04:03:24 auw2 sshd\[25089\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.91.200.186
2020-02-13 05:55:22
209.97.168.18 attackbots
Hits on port : 85
2020-02-13 05:49:54

Recently Reported IPs

105.229.118.55 195.233.179.131 84.17.59.41 124.251.199.160
36.227.121.144 89.141.98.72 41.72.29.140 210.195.205.70
47.29.54.53 79.22.95.205 109.224.125.145 113.204.67.164
118.69.13.37 88.78.178.159 182.219.16.170 116.138.165.129
87.155.70.96 82.17.155.212 144.162.242.97 14.20.244.44