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: San Antonio

Region: Texas

Country: United States

Internet Service Provider: AT&T

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

;; QUESTION SECTION:
;12.197.196.134.			IN	A

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

;; Query time: 18 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Jan 20 20:44:43 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 134.196.197.12.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 134.196.197.12.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
207.154.229.50 attackspambots
Oct 28 07:54:59 localhost sshd\[35116\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=207.154.229.50  user=root
Oct 28 07:55:01 localhost sshd\[35116\]: Failed password for root from 207.154.229.50 port 55044 ssh2
Oct 28 07:58:36 localhost sshd\[35227\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=207.154.229.50  user=root
Oct 28 07:58:38 localhost sshd\[35227\]: Failed password for root from 207.154.229.50 port 37330 ssh2
Oct 28 08:02:17 localhost sshd\[35329\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=207.154.229.50  user=root
...
2019-10-28 16:02:48
211.52.135.79 attackbotsspam
23/tcp
[2019-10-28]1pkt
2019-10-28 15:41:20
139.155.5.132 attackspam
Oct 28 01:56:03 plusreed sshd[30371]: Invalid user Official@123 from 139.155.5.132
...
2019-10-28 15:41:51
14.29.207.59 attackspambots
Oct 28 07:12:04 xeon sshd[5757]: Failed password for invalid user tom from 14.29.207.59 port 37868 ssh2
2019-10-28 15:55:39
103.114.107.125 attackspambots
Oct 28 10:51:36 lcl-usvr-01 sshd[2356]: refused connect from 103.114.107.125 (103.114.107.125)
Oct 28 10:51:36 lcl-usvr-01 sshd[2357]: refused connect from 103.114.107.125 (103.114.107.125)
2019-10-28 15:40:40
106.13.95.27 attackspam
Automatic report - SSH Brute-Force Attack
2019-10-28 15:56:45
184.75.211.142 attackspambots
(From david@davidmelnichuk.com) I saw this form on your site, and I submitted it. Now you’re reading this, so that means it works. Awesome! But that’s not enough.

For this form to make your business money, people have to respond to you when you reach out to them. Don’t you hate it when they never answer, or by the time you get back to them, they already decided to do business with your competitor? This ends today. I made a free video tutorial that shows you how to setup an immediate SMS message and email response to go out to every lead that submits this form so you can start a conversation while they are still thinking about your services.

If you contact a lead in the first 2 minutes after they’ve submitted this web form, they’re 100x more likely to respond and 78% of customers buy from the first responder. Check out my free tutorial on how to set this up: http://bit.ly/how-to-setup-an-automatic-sms-and-email

What’s the catch? Nothing. My step-by-step training here is completely free and will show y
2019-10-28 15:40:16
88.129.208.35 attackspambots
Honeypot attack, port: 23, PTR: h88-129-208-35.cust.a3fiber.se.
2019-10-28 16:02:08
204.12.192.89 attackspambots
445/tcp 445/tcp 445/tcp
[2019-10-28]3pkt
2019-10-28 15:48:53
60.248.199.194 attackspam
Oct 28 07:52:48 ArkNodeAT sshd\[10445\]: Invalid user gestore from 60.248.199.194
Oct 28 07:52:48 ArkNodeAT sshd\[10445\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=60.248.199.194
Oct 28 07:52:50 ArkNodeAT sshd\[10445\]: Failed password for invalid user gestore from 60.248.199.194 port 42785 ssh2
2019-10-28 15:44:11
125.112.109.238 attackbotsspam
Port 1433 Scan
2019-10-28 15:37:09
118.25.150.90 attack
2019-10-28T06:54:43.026115shield sshd\[4455\]: Invalid user password1 from 118.25.150.90 port 50069
2019-10-28T06:54:43.030446shield sshd\[4455\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.25.150.90
2019-10-28T06:54:45.021306shield sshd\[4455\]: Failed password for invalid user password1 from 118.25.150.90 port 50069 ssh2
2019-10-28T06:59:34.258998shield sshd\[5079\]: Invalid user !\(\*\&!\$\)ytmdwihc from 118.25.150.90 port 40705
2019-10-28T06:59:34.263160shield sshd\[5079\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.25.150.90
2019-10-28 16:01:47
12.203.68.2 attackbots
445/tcp
[2019-10-28]1pkt
2019-10-28 16:02:35
145.239.196.2 attackspambots
Oct 28 08:48:26 SilenceServices sshd[27283]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=145.239.196.2
Oct 28 08:48:28 SilenceServices sshd[27283]: Failed password for invalid user drschwan from 145.239.196.2 port 51832 ssh2
Oct 28 08:51:53 SilenceServices sshd[29436]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=145.239.196.2
2019-10-28 16:03:09
211.232.39.8 attack
Oct 28 07:47:49 localhost sshd\[34898\]: Invalid user maroon from 211.232.39.8 port 21486
Oct 28 07:47:49 localhost sshd\[34898\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.232.39.8
Oct 28 07:47:51 localhost sshd\[34898\]: Failed password for invalid user maroon from 211.232.39.8 port 21486 ssh2
Oct 28 07:52:15 localhost sshd\[35042\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.232.39.8  user=root
Oct 28 07:52:18 localhost sshd\[35042\]: Failed password for root from 211.232.39.8 port 61162 ssh2
...
2019-10-28 15:59:47

Recently Reported IPs

76.242.205.73 83.44.255.53 36.120.158.157 109.48.168.12
7.43.28.55 91.166.186.154 88.56.20.102 130.151.222.55
211.130.68.141 19.163.49.1 63.85.27.61 38.40.2.174
88.218.252.112 85.248.215.188 235.225.117.135 115.190.151.170
146.179.173.223 0.29.184.37 136.49.248.105 104.41.19.244