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

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

;; QUESTION SECTION:
;136.243.169.12.			IN	A

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

;; Query time: 64 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 11:47:21 CST 2022
;; MSG SIZE  rcvd: 107
Host info
12.169.243.136.in-addr.arpa domain name pointer fo5.toppreise.ch.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
12.169.243.136.in-addr.arpa	name = fo5.toppreise.ch.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
106.12.193.217 attack
(sshd) Failed SSH login from 106.12.193.217 (CN/China/-): 5 in the last 3600 secs
2020-04-09 08:36:16
54.38.242.233 attack
Repeated brute force against a port
2020-04-09 08:29:06
144.2.64.119 attack
Automatic report - SSH Brute-Force Attack
2020-04-09 08:09:15
209.58.157.196 attackspam
(From eric@talkwithwebvisitor.com) Hey, my name’s Eric and for just a second, imagine this…

- Someone does a search and winds up at castelluccichiropractic.com.

- They hang out for a minute to check it out.  “I’m interested… but… maybe…”

- And then they hit the back button and check out the other search results instead. 

- Bottom line – you got an eyeball, but nothing else to show for it.

- There they go.

This isn’t really your fault – it happens a LOT – studies show 7 out of 10 visitors to any site disappear without leaving a trace.

But you CAN fix that.

Talk With Web Visitor is a software widget that’s works on your site, ready to capture any visitor’s Name, Email address and Phone Number.  It lets you know right then and there – enabling you to call that lead while they’re literally looking over your site.

CLICK HERE http://www.talkwithwebvisitor.com to try out a Live Demo with Talk With Web Visitor now to see exactly how it works.

Time is money when it comes to connecting wit
2020-04-09 08:01:00
103.116.24.159 attackbotsspam
port scan and connect, tcp 23 (telnet)
2020-04-09 08:25:21
82.125.248.222 attackspam
Apr  9 02:15:45 odroid64 sshd\[3357\]: Invalid user test from 82.125.248.222
Apr  9 02:15:45 odroid64 sshd\[3357\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=82.125.248.222
...
2020-04-09 08:28:43
51.38.225.124 attack
Apr  9 02:28:26 ArkNodeAT sshd\[14112\]: Invalid user simey from 51.38.225.124
Apr  9 02:28:26 ArkNodeAT sshd\[14112\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.38.225.124
Apr  9 02:28:28 ArkNodeAT sshd\[14112\]: Failed password for invalid user simey from 51.38.225.124 port 46460 ssh2
2020-04-09 08:29:19
37.49.230.32 attack
SIP Server BruteForce Attack
2020-04-09 08:00:32
213.177.106.126 attackspambots
Apr  9 01:51:54 mail sshd[13228]: Invalid user test from 213.177.106.126
Apr  9 01:51:54 mail sshd[13228]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=213.177.106.126
Apr  9 01:51:54 mail sshd[13228]: Invalid user test from 213.177.106.126
Apr  9 01:51:56 mail sshd[13228]: Failed password for invalid user test from 213.177.106.126 port 60636 ssh2
...
2020-04-09 08:31:11
183.89.243.167 attackspam
Brute force attempt
2020-04-09 08:28:21
113.128.221.50 attackspam
RDP Brute-Force
2020-04-09 07:55:47
134.122.29.53 attackspambots
SSH bruteforce (Triggered fail2ban)
2020-04-09 08:15:21
162.243.129.124 attackbots
Automatic report - Port Scan Attack
2020-04-09 08:36:47
104.131.139.147 attack
Automatic report - XMLRPC Attack
2020-04-09 08:24:41
162.243.130.188 attack
trying to access non-authorized port
2020-04-09 08:26:03

Recently Reported IPs

136.243.169.101 136.243.169.141 136.243.17.205 136.243.171.217
136.243.172.216 136.243.174.169 136.243.173.46 6.213.17.250
136.243.175.207 136.243.174.232 136.243.176.31 136.243.177.171
136.243.177.20 136.243.177.43 136.243.177.66 136.243.178.122
136.243.18.213 136.243.179.64 136.243.189.16 136.243.18.218