City: Fresno
Region: California
Country: United States
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 68.254.253.92
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 58193
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;68.254.253.92. IN A
;; AUTHORITY SECTION:
. 509 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2020080100 1800 900 604800 86400
;; Query time: 22 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Aug 01 20:54:30 CST 2020
;; MSG SIZE rcvd: 117
92.253.254.68.in-addr.arpa domain name pointer 68-254-253-92.lightspeed.frsnca.sbcglobal.net.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
92.253.254.68.in-addr.arpa name = 68-254-253-92.lightspeed.frsnca.sbcglobal.net.
Authoritative answers can be found from:
IP | Type | Details | Datetime |
---|---|---|---|
66.70.214.177 | attack | 2019-10-31T20:02:45.742463www.arvenenaske.de sshd[989425]: Invalid user regina from 66.70.214.177 port 59166 2019-10-31T20:02:45.747561www.arvenenaske.de sshd[989425]: pam_sss(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=66.70.214.177 user=regina 2019-10-31T20:02:45.748266www.arvenenaske.de sshd[989425]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=66.70.214.177 2019-10-31T20:02:45.742463www.arvenenaske.de sshd[989425]: Invalid user regina from 66.70.214.177 port 59166 2019-10-31T20:02:47.494327www.arvenenaske.de sshd[989425]: Failed password for invalid user regina from 66.70.214.177 port 59166 ssh2 2019-10-31T20:06:55.016263www.arvenenaske.de sshd[989469]: Invalid user chef from 66.70.214.177 port 43008 2019-10-31T20:06:55.021825www.arvenenaske.de sshd[989469]: pam_sss(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=66.70.214.177 user=chef 2019-10-31T20:06:55.022........ ------------------------------ |
2019-11-02 13:11:48 |
139.199.158.14 | attackbots | Nov 2 05:25:08 vps647732 sshd[32230]: Failed password for root from 139.199.158.14 port 39211 ssh2 Nov 2 05:29:32 vps647732 sshd[32301]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.199.158.14 ... |
2019-11-02 13:29:23 |
185.36.219.24 | attackspambots | slow and persistent scanner |
2019-11-02 13:09:59 |
107.172.227.120 | attack | (From eric@talkwithcustomer.com) Hello abcchiropractic.net, 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 abcchiropractic.net. - 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 abcchiropractic.net, 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 famo |
2019-11-02 13:15:13 |
89.248.174.215 | attackspambots | ET CINS Active Threat Intelligence Poor Reputation IP group 87 - port: 8089 proto: TCP cat: Misc Attack |
2019-11-02 13:08:47 |
45.61.172.60 | attackspambots | (From eric@talkwithcustomer.com) Hello abcchiropractic.net, 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 abcchiropractic.net. - 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 abcchiropractic.net, 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 famo |
2019-11-02 13:14:51 |
123.176.5.232 | attackspambots | Chat Spam |
2019-11-02 13:47:46 |
65.98.110.43 | attack | IP Ban Report : https://help-dysk.pl/wordpress-firewall-plugins/ip/65.98.110.43/ SA - 1H : (6) Protection Against DDoS WordPress plugin : "odzyskiwanie danych help-dysk" IP Address Ranges by Country : SA NAME ASN : ASN25653 IP : 65.98.110.43 CIDR : 65.98.110.0/23 PREFIX COUNT : 156 UNIQUE IP COUNT : 113152 ATTACKS DETECTED ASN25653 : 1H - 1 3H - 1 6H - 1 12H - 1 24H - 1 DateTime : 2019-11-02 04:53:06 INFO : Port MAX SCAN Scan Detected and Blocked by ADMIN - data recovery |
2019-11-02 13:47:13 |
222.186.42.4 | attack | Nov 2 08:25:45 server sshd\[17229\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.42.4 user=root Nov 2 08:25:47 server sshd\[17229\]: Failed password for root from 222.186.42.4 port 13154 ssh2 Nov 2 08:25:47 server sshd\[17242\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.42.4 user=root Nov 2 08:25:48 server sshd\[17246\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.42.4 user=root Nov 2 08:25:49 server sshd\[17242\]: Failed password for root from 222.186.42.4 port 42758 ssh2 ... |
2019-11-02 13:30:03 |
178.0.239.93 | attackspam | IP Ban Report : https://help-dysk.pl/wordpress-firewall-plugins/ip/178.0.239.93/ DE - 1H : (56) Protection Against DDoS WordPress plugin : "odzyskiwanie danych help-dysk" IP Address Ranges by Country : DE NAME ASN : ASN3209 IP : 178.0.239.93 CIDR : 178.0.0.0/13 PREFIX COUNT : 165 UNIQUE IP COUNT : 8314624 ATTACKS DETECTED ASN3209 : 1H - 1 3H - 3 6H - 4 12H - 4 24H - 8 DateTime : 2019-11-02 04:54:02 INFO : Port Scan TELNET Detected and Blocked by ADMIN - data recovery |
2019-11-02 13:10:28 |
106.13.150.163 | attackspambots | Nov 1 18:32:03 web1 sshd\[21399\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.150.163 user=root Nov 1 18:32:05 web1 sshd\[21399\]: Failed password for root from 106.13.150.163 port 47364 ssh2 Nov 1 18:36:50 web1 sshd\[21849\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.150.163 user=root Nov 1 18:36:53 web1 sshd\[21849\]: Failed password for root from 106.13.150.163 port 54828 ssh2 Nov 1 18:41:54 web1 sshd\[22365\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.150.163 user=root |
2019-11-02 13:03:16 |
182.61.162.54 | attack | Nov 2 07:25:32 server sshd\[21248\]: User root from 182.61.162.54 not allowed because listed in DenyUsers Nov 2 07:25:32 server sshd\[21248\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.162.54 user=root Nov 2 07:25:34 server sshd\[21248\]: Failed password for invalid user root from 182.61.162.54 port 50272 ssh2 Nov 2 07:30:16 server sshd\[23828\]: User root from 182.61.162.54 not allowed because listed in DenyUsers Nov 2 07:30:16 server sshd\[23828\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.162.54 user=root |
2019-11-02 13:46:41 |
122.141.177.112 | attackbotsspam | Tried sshing with brute force. |
2019-11-02 13:08:17 |
83.78.88.103 | attackspambots | Nov 2 01:21:53 debian sshd\[17594\]: Invalid user agosta from 83.78.88.103 port 57278 Nov 2 01:21:53 debian sshd\[17594\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=83.78.88.103 Nov 2 01:21:55 debian sshd\[17594\]: Failed password for invalid user agosta from 83.78.88.103 port 57278 ssh2 ... |
2019-11-02 13:25:46 |
92.53.90.179 | attackspam | Port scan on 6 port(s): 5607 5769 5916 5950 6270 6371 |
2019-11-02 13:17:56 |