City: unknown
Region: unknown
Country: United States of America (the)
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 134.56.254.139
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 36883
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;134.56.254.139. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025021000 1800 900 604800 86400
;; Query time: 13 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 10 14:15:02 CST 2025
;; MSG SIZE rcvd: 107139.254.56.134.in-addr.arpa domain name pointer 134.56.254.139.hwccustomers.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
139.254.56.134.in-addr.arpa name = 134.56.254.139.hwccustomers.com.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 46.102.175.105 | attack | firewall-block, port(s): 5564/tcp |
2020-04-16 22:06:17 |
| 45.152.34.24 | attack | (From eric@talkwithwebvisitor.com) Good day, My name is Eric and unlike a lot of emails you might get, I wanted to instead provide you with a word of encouragement – Congratulations What for? Part of my job is to check out websites and the work you’ve done with plinkechiropractic.com definitely stands out. It’s clear you took building a website seriously and made a real investment of time and resources into making it top quality. There is, however, a catch… more accurately, a question… So when someone like me happens to find your site – maybe at the top of the search results (nice job BTW) or just through a random link, how do you know? More importantly, how do you make a connection with that person? Studies show that 7 out of 10 visitors don’t stick around – they’re there one second and then gone with the wind. Here’s a way to create INSTANT engagement that you may not have known about… Talk With Web Visitor is a software widget that’s works on your site, ready to capture |
2020-04-16 21:53:05 |
| 198.199.103.92 | attackspam | Apr 16 14:01:44 ns382633 sshd\[26144\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=198.199.103.92 user=root Apr 16 14:01:46 ns382633 sshd\[26144\]: Failed password for root from 198.199.103.92 port 43779 ssh2 Apr 16 14:14:37 ns382633 sshd\[28654\]: Invalid user oracle from 198.199.103.92 port 42118 Apr 16 14:14:37 ns382633 sshd\[28654\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=198.199.103.92 Apr 16 14:14:39 ns382633 sshd\[28654\]: Failed password for invalid user oracle from 198.199.103.92 port 42118 ssh2 |
2020-04-16 21:54:41 |
| 178.219.16.88 | attack | Apr 16 14:14:20 [host] sshd[29212]: Invalid user g Apr 16 14:14:20 [host] sshd[29212]: pam_unix(sshd: Apr 16 14:14:22 [host] sshd[29212]: Failed passwor |
2020-04-16 22:14:33 |
| 109.169.212.248 | attackbotsspam | 1587039273 - 04/16/2020 14:14:33 Host: 109.169.212.248/109.169.212.248 Port: 445 TCP Blocked |
2020-04-16 22:03:48 |
| 112.85.42.188 | attackspam | 04/16/2020-10:14:29.845997 112.85.42.188 Protocol: 6 ET SCAN Potential SSH Scan |
2020-04-16 22:15:02 |
| 103.145.12.45 | attack | voip attacker |
2020-04-16 22:13:49 |
| 46.101.80.244 | attackbotsspam | Apr 16 15:35:54 pkdns2 sshd\[38196\]: Invalid user git from 46.101.80.244Apr 16 15:35:56 pkdns2 sshd\[38196\]: Failed password for invalid user git from 46.101.80.244 port 43552 ssh2Apr 16 15:39:56 pkdns2 sshd\[38349\]: Invalid user vu from 46.101.80.244Apr 16 15:39:58 pkdns2 sshd\[38349\]: Failed password for invalid user vu from 46.101.80.244 port 57236 ssh2Apr 16 15:43:59 pkdns2 sshd\[38542\]: Invalid user e from 46.101.80.244Apr 16 15:44:02 pkdns2 sshd\[38542\]: Failed password for invalid user e from 46.101.80.244 port 42686 ssh2 ... |
2020-04-16 22:06:39 |
| 182.180.128.132 | attackbotsspam | Apr 16 15:36:18 haigwepa sshd[2457]: Failed password for root from 182.180.128.132 port 54494 ssh2 ... |
2020-04-16 21:59:14 |
| 176.113.115.42 | attack | Apr 16 14:43:56 ns381471 sshd[12852]: Failed password for root from 176.113.115.42 port 39994 ssh2 |
2020-04-16 21:59:38 |
| 80.211.164.5 | attackbotsspam | Apr 16 15:18:15 * sshd[4479]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.211.164.5 Apr 16 15:18:17 * sshd[4479]: Failed password for invalid user couchdb from 80.211.164.5 port 53762 ssh2 |
2020-04-16 21:56:56 |
| 91.192.46.209 | attackbotsspam | Apr 16 14:14:43 prod4 vsftpd\[19679\]: \[anonymous\] FAIL LOGIN: Client "91.192.46.209" Apr 16 14:14:44 prod4 vsftpd\[19689\]: \[www\] FAIL LOGIN: Client "91.192.46.209" Apr 16 14:14:45 prod4 vsftpd\[19694\]: \[www\] FAIL LOGIN: Client "91.192.46.209" Apr 16 14:14:47 prod4 vsftpd\[19709\]: \[www\] FAIL LOGIN: Client "91.192.46.209" Apr 16 14:14:48 prod4 vsftpd\[19718\]: \[www\] FAIL LOGIN: Client "91.192.46.209" ... |
2020-04-16 21:45:18 |
| 73.96.141.67 | attack | (sshd) Failed SSH login from 73.96.141.67 (US/United States/c-73-96-141-67.hsd1.or.comcast.net): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Apr 16 14:57:46 s1 sshd[744]: Invalid user ftpuser from 73.96.141.67 port 60880 Apr 16 14:57:48 s1 sshd[744]: Failed password for invalid user ftpuser from 73.96.141.67 port 60880 ssh2 Apr 16 15:10:21 s1 sshd[2238]: Invalid user ed from 73.96.141.67 port 52088 Apr 16 15:10:23 s1 sshd[2238]: Failed password for invalid user ed from 73.96.141.67 port 52088 ssh2 Apr 16 15:14:12 s1 sshd[2468]: Invalid user qy from 73.96.141.67 port 59896 |
2020-04-16 22:19:12 |
| 180.250.108.133 | attackspambots | (sshd) Failed SSH login from 180.250.108.133 (ID/Indonesia/-): 2 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Apr 16 14:14:17 ubnt-55d23 sshd[8984]: Invalid user test from 180.250.108.133 port 55714 Apr 16 14:14:19 ubnt-55d23 sshd[8984]: Failed password for invalid user test from 180.250.108.133 port 55714 ssh2 |
2020-04-16 22:14:13 |
| 185.175.93.25 | attackspambots | 04/16/2020-09:58:33.767061 185.175.93.25 Protocol: 6 ET DROP Dshield Block Listed Source group 1 |
2020-04-16 22:20:02 |