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

Region: Nairobi Province

Country: Kenya

Internet Service Provider: Safaricom

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

;; QUESTION SECTION:
;196.104.180.94.			IN	A

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

;; Query time: 60 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Jan 18 00:01:45 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 94.180.104.196.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 94.180.104.196.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
180.242.183.230 attack
Honeypot attack, port: 445, PTR: PTR record not found
2020-01-11 07:00:11
210.109.111.76 attack
Honeypot attack, port: 445, PTR: PTR record not found
2020-01-11 06:56:57
125.214.58.131 attackspam
Honeypot attack, port: 445, PTR: PTR record not found
2020-01-11 06:57:16
37.123.150.48 attackbots
Honeypot attack, port: 5555, PTR: h-150-48.A317.priv.bahnhof.se.
2020-01-11 06:56:34
71.67.116.159 attackbots
Honeypot attack, port: 5555, PTR: cpe-71-67-116-159.cinci.res.rr.com.
2020-01-11 06:29:11
115.74.208.168 attackbots
Honeypot attack, port: 445, PTR: adsl.viettel.vn.
2020-01-11 06:52:23
95.90.154.148 attackspambots
Jan 10 23:05:59 lukav-desktop sshd\[11625\]: Invalid user render123 from 95.90.154.148
Jan 10 23:05:59 lukav-desktop sshd\[11625\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=95.90.154.148
Jan 10 23:06:01 lukav-desktop sshd\[11625\]: Failed password for invalid user render123 from 95.90.154.148 port 40759 ssh2
Jan 10 23:10:18 lukav-desktop sshd\[19234\]: Invalid user housecat from 95.90.154.148
Jan 10 23:10:18 lukav-desktop sshd\[19234\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=95.90.154.148
2020-01-11 06:51:07
58.250.89.46 attackbotsspam
Jan 10 16:36:08 ny01 sshd[12843]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.250.89.46
Jan 10 16:36:10 ny01 sshd[12843]: Failed password for invalid user 2yTZFE5 from 58.250.89.46 port 37835 ssh2
Jan 10 16:39:12 ny01 sshd[13147]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.250.89.46
2020-01-11 06:32:15
106.75.78.135 attackbotsspam
Automatic report - Banned IP Access
2020-01-11 06:30:40
192.210.201.220 attack
(From eric@talkwithcustomer.com) Hello wardchiropractic.com,

People ask, “why does TalkWithCustomer work so well?”

It’s simple.

TalkWithCustomer enables you to connect with a prospective customer at EXACTLY the Perfect Time.

- NOT one week, two weeks, three weeks after they’ve checked out your website wardchiropractic.com.
- NOT with a form letter style email that looks like it was written by a bot.
- NOT with a robocall that could come at any time out of the blue.

TalkWithCustomer connects you to that person within seconds of THEM asking to hear from YOU.

They kick off the conversation.

They take that first step.

They ask to hear from you regarding what you have to offer and how it can make their life better. 

And it happens almost immediately. In real time. While they’re still looking over your website wardchiropractic.com, trying to make up their mind whether you are right for them.

When you connect with them at that very moment it’s the ultimate in Perfect Timing – as one f
2020-01-11 06:48:52
146.168.2.84 attackspambots
Invalid user lg from 146.168.2.84 port 41322
2020-01-11 06:45:09
103.126.100.179 attackbots
Jan 10 21:49:06 h2812830 sshd[15544]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.126.100.179  user=root
Jan 10 21:49:08 h2812830 sshd[15544]: Failed password for root from 103.126.100.179 port 36296 ssh2
Jan 10 22:10:29 h2812830 sshd[16713]: Invalid user 0 from 103.126.100.179 port 49640
Jan 10 22:10:29 h2812830 sshd[16713]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.126.100.179
Jan 10 22:10:29 h2812830 sshd[16713]: Invalid user 0 from 103.126.100.179 port 49640
Jan 10 22:10:31 h2812830 sshd[16713]: Failed password for invalid user 0 from 103.126.100.179 port 49640 ssh2
...
2020-01-11 06:33:48
46.38.144.17 attackspambots
Jan 10 23:20:47 vmanager6029 postfix/smtpd\[16432\]: warning: unknown\[46.38.144.17\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jan 10 23:21:35 vmanager6029 postfix/smtpd\[16432\]: warning: unknown\[46.38.144.17\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
2020-01-11 06:32:37
96.84.240.89 attack
Jan 10 19:52:13 vps46666688 sshd[20877]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=96.84.240.89
Jan 10 19:52:15 vps46666688 sshd[20877]: Failed password for invalid user apache from 96.84.240.89 port 39590 ssh2
...
2020-01-11 07:02:14
210.121.116.98 attackbotsspam
Honeypot attack, port: 81, PTR: PTR record not found
2020-01-11 06:52:50

Recently Reported IPs

236.55.232.47 180.231.225.187 110.3.55.210 127.116.206.130
217.31.29.36 135.121.12.179 5.195.124.247 194.150.220.147
122.135.88.53 185.232.22.146 182.235.216.206 238.69.1.16
214.113.93.214 120.167.64.125 220.160.87.75 66.226.51.170
56.195.66.192 117.17.198.101 160.3.108.123 111.90.150.64