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

;; QUESTION SECTION:
;34.139.243.12.			IN	A

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

;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 16 14:27:31 CST 2025
;; MSG SIZE  rcvd: 106
Host info
12.243.139.34.in-addr.arpa domain name pointer 12.243.139.34.bc.googleusercontent.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
12.243.139.34.in-addr.arpa	name = 12.243.139.34.bc.googleusercontent.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
83.28.47.230 attack
Jan 16 11:00:50 site3 sshd\[244555\]: Invalid user ts from 83.28.47.230
Jan 16 11:00:50 site3 sshd\[244555\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=83.28.47.230
Jan 16 11:00:52 site3 sshd\[244555\]: Failed password for invalid user ts from 83.28.47.230 port 60662 ssh2
Jan 16 11:02:58 site3 sshd\[244570\]: Invalid user root01 from 83.28.47.230
Jan 16 11:02:58 site3 sshd\[244570\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=83.28.47.230
...
2020-01-16 17:13:06
91.244.74.13 attackbotsspam
1579150103 - 01/16/2020 05:48:23 Host: 91.244.74.13/91.244.74.13 Port: 445 TCP Blocked
2020-01-16 17:16:00
139.199.228.154 attackbots
Unauthorized connection attempt detected from IP address 139.199.228.154 to port 2220 [J]
2020-01-16 16:54:15
198.46.222.123 attack
(From eric@talkwithcustomer.com) 
Hi,

Let’s take a quick trip to Tomorrow-land.

I’m not talking about a theme park, I’m talking about your business’s future…

Don’t worry, we won’t even need a crystal ball.  

Just imagine… 

… a future where the money you invest in driving traffic to your site andoverspinecenter.com pays off with tons of calls from qualified leads.
 
And the difference between what you experienced in the past is staggering – you’re seeing 10X, 20X, 50X, even up to a 100X more leads coming from your website andoverspinecenter.com.  Leads that are already engaged with what you have to offer and are ready to learn more and even open their wallets.

Seeing all this taking place in your business, you think back: What did I do only a short time ago that made such a huge difference?

And then it hits you: You took advantage of a free 14 day Test Drive of TalkWithCustomer.

You installed TalkWithCustomer on andoverspinecenter.com – it was a snap.

And practically overnight cus
2020-01-16 17:20:49
138.197.147.128 attack
Automatic report - SSH Brute-Force Attack
2020-01-16 17:26:30
80.211.78.155 attack
Unauthorized connection attempt detected from IP address 80.211.78.155 to port 2220 [J]
2020-01-16 16:56:37
81.148.222.42 attack
Unauthorized connection attempt detected from IP address 81.148.222.42 to port 9000 [J]
2020-01-16 16:49:04
167.172.139.65 attackspam
167.172.139.65 - - \[16/Jan/2020:08:09:16 +0100\] "POST /wp-login.php HTTP/1.0" 200 7427 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
167.172.139.65 - - \[16/Jan/2020:08:09:23 +0100\] "POST /wp-login.php HTTP/1.0" 200 7242 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
167.172.139.65 - - \[16/Jan/2020:08:09:29 +0100\] "POST /wp-login.php HTTP/1.0" 200 7239 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
2020-01-16 16:49:56
74.207.242.199 attackspambots
firewall-block, port(s): 37/tcp
2020-01-16 17:06:00
107.180.123.17 attackspam
localhost:80 107.180.123.17 - - [16/Jan/2020:05:48:19 +0100] "POST /xmlrpc.php HTTP/1.1" 301 449 "-" "Windows Live Writter"
masters-of-media.de 107.180.123.17 [16/Jan/2020:05:48:20 +0100] "POST /xmlrpc.php HTTP/1.1" 200 4254 "-" "Windows Live Writter"
2020-01-16 17:17:39
51.38.37.154 attackspambots
51.38.37.154 - - [16/Jan/2020:04:48:27 +0000] "POST /wp-login.php HTTP/1.1" 200 6409 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
51.38.37.154 - - [16/Jan/2020:04:48:28 +0000] "POST /xmlrpc.php HTTP/1.1" 200 403 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
...
2020-01-16 17:11:53
5.101.219.82 attack
B: zzZZzz blocked content access
2020-01-16 17:18:30
207.180.250.180 attack
Jan 16 09:10:50 ArkNodeAT sshd\[15318\]: Invalid user leslie from 207.180.250.180
Jan 16 09:10:50 ArkNodeAT sshd\[15318\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=207.180.250.180
Jan 16 09:10:52 ArkNodeAT sshd\[15318\]: Failed password for invalid user leslie from 207.180.250.180 port 60254 ssh2
2020-01-16 17:09:05
222.186.175.150 attackbotsspam
SSH Brute-Force reported by Fail2Ban
2020-01-16 17:08:29
59.32.99.7 attackbotsspam
Port scan on 1 port(s): 21
2020-01-16 17:02:00

Recently Reported IPs

180.190.37.76 211.132.19.158 36.135.187.45 197.121.73.120
20.130.81.127 63.141.26.79 38.13.175.215 230.217.235.84
184.226.64.79 147.163.50.196 255.162.95.143 250.154.185.80
157.169.169.107 124.98.24.55 92.205.199.186 227.37.229.143
101.199.162.120 208.218.1.61 206.190.84.54 251.136.195.74