City: unknown
Region: unknown
Country: Norway
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 148.121.243.254
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 26665
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;148.121.243.254. IN A
;; AUTHORITY SECTION:
. 168 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2021122701 1800 900 604800 86400
;; Query time: 20 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Dec 28 03:10:43 CST 2021
;; MSG SIZE rcvd: 108254.243.121.148.in-addr.arpa domain name pointer 254.243.121.148.in-addr.arpa.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
254.243.121.148.in-addr.arpa name = 254.243.121.148.in-addr.arpa.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 203.163.251.232 | attack | 23/tcp [2020-05-06]1pkt |
2020-05-07 00:18:25 |
| 107.173.204.146 | attackspambots | (From eric@talkwithwebvisitor.com) Hey, this is Eric and I ran across advancedchirosolutions.com a few minutes ago. Looks great… but now what? By that I mean, when someone like me finds your website – either through Search or just bouncing around – what happens next? Do you get a lot of leads from your site, or at least enough to make you happy? Honestly, most business websites fall a bit short when it comes to generating paying customers. Studies show that 70% of a site’s visitors disappear and are gone forever after just a moment. Here’s an idea… How about making it really EASY for every visitor who shows up to get a personal phone call you as soon as they hit your site… You can – 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 signals you the moment they let you know they’re interested – so that you can talk to that lead while they’re literally looking over your site. CLICK HERE http: |
2020-05-07 00:22:45 |
| 179.43.174.220 | attackspambots | 0,16-04/34 [bc01/m110] PostRequest-Spammer scoring: harare01 |
2020-05-07 00:14:18 |
| 167.99.194.54 | attack | May 4 01:16:11 pi sshd[3952]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.194.54 May 4 01:16:13 pi sshd[3952]: Failed password for invalid user cellphone from 167.99.194.54 port 39888 ssh2 |
2020-05-07 00:34:56 |
| 182.76.160.138 | attackspambots | May 6 06:08:56 server1 sshd\[27600\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.76.160.138 user=root May 6 06:08:58 server1 sshd\[27600\]: Failed password for root from 182.76.160.138 port 50790 ssh2 May 6 06:18:29 server1 sshd\[30790\]: Invalid user dokuwiki from 182.76.160.138 May 6 06:18:29 server1 sshd\[30790\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.76.160.138 May 6 06:18:31 server1 sshd\[30790\]: Failed password for invalid user dokuwiki from 182.76.160.138 port 53616 ssh2 ... |
2020-05-07 00:49:49 |
| 74.141.132.233 | attack | May 6 22:02:11 web1 sshd[809]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=74.141.132.233 user=root May 6 22:02:13 web1 sshd[809]: Failed password for root from 74.141.132.233 port 43130 ssh2 May 6 22:11:43 web1 sshd[5914]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=74.141.132.233 user=root May 6 22:11:46 web1 sshd[5914]: Failed password for root from 74.141.132.233 port 51244 ssh2 May 6 22:17:08 web1 sshd[7904]: Invalid user kenny from 74.141.132.233 port 60366 May 6 22:17:09 web1 sshd[7904]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=74.141.132.233 May 6 22:17:08 web1 sshd[7904]: Invalid user kenny from 74.141.132.233 port 60366 May 6 22:17:10 web1 sshd[7904]: Failed password for invalid user kenny from 74.141.132.233 port 60366 ssh2 May 6 22:22:20 web1 sshd[9621]: Invalid user csvn from 74.141.132.233 port 41262 ... |
2020-05-07 00:19:27 |
| 107.172.230.108 | attackbotsspam | (From eric@talkwithwebvisitor.com) Hey, this is Eric and I ran across advancedchirosolutions.com a few minutes ago. Looks great… but now what? By that I mean, when someone like me finds your website – either through Search or just bouncing around – what happens next? Do you get a lot of leads from your site, or at least enough to make you happy? Honestly, most business websites fall a bit short when it comes to generating paying customers. Studies show that 70% of a site’s visitors disappear and are gone forever after just a moment. Here’s an idea… How about making it really EASY for every visitor who shows up to get a personal phone call you as soon as they hit your site… You can – 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 signals you the moment they let you know they’re interested – so that you can talk to that lead while they’re literally looking over your site. CLICK HERE http: |
2020-05-07 00:28:09 |
| 88.12.116.189 | attackbotsspam | May 6 11:04:46 XXX sshd[560]: Invalid user user from 88.12.116.189 port 34458 |
2020-05-07 00:16:52 |
| 85.209.0.104 | attack | May 6 13:59:58 ns3164893 sshd[21050]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=85.209.0.104 user=root May 6 14:00:00 ns3164893 sshd[21050]: Failed password for root from 85.209.0.104 port 5596 ssh2 ... |
2020-05-07 00:12:40 |
| 198.108.67.24 | attackspambots | firewall-block, port(s): 8088/tcp |
2020-05-07 00:47:22 |
| 185.50.149.10 | attack | May 6 18:27:21 relay postfix/smtpd\[17200\]: warning: unknown\[185.50.149.10\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 May 6 18:27:46 relay postfix/smtpd\[17242\]: warning: unknown\[185.50.149.10\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 May 6 18:30:16 relay postfix/smtpd\[17199\]: warning: unknown\[185.50.149.10\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 May 6 18:30:34 relay postfix/smtpd\[17239\]: warning: unknown\[185.50.149.10\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 May 6 18:36:58 relay postfix/smtpd\[17200\]: warning: unknown\[185.50.149.10\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 ... |
2020-05-07 00:41:02 |
| 183.82.105.103 | attackspam | May 6 23:17:10 webhost01 sshd[15737]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.82.105.103 May 6 23:17:12 webhost01 sshd[15737]: Failed password for invalid user admin from 183.82.105.103 port 51944 ssh2 ... |
2020-05-07 00:24:55 |
| 37.211.77.84 | attackspam | May 6 13:59:18 mail sshd[14158]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.211.77.84 May 6 13:59:19 mail sshd[14158]: Failed password for invalid user v from 37.211.77.84 port 38268 ssh2 ... |
2020-05-07 00:53:25 |
| 180.166.184.66 | attackspambots | May 6 16:28:51 OPSO sshd\[7542\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.166.184.66 user=root May 6 16:28:53 OPSO sshd\[7542\]: Failed password for root from 180.166.184.66 port 44857 ssh2 May 6 16:33:00 OPSO sshd\[8536\]: Invalid user master from 180.166.184.66 port 49048 May 6 16:33:00 OPSO sshd\[8536\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.166.184.66 May 6 16:33:02 OPSO sshd\[8536\]: Failed password for invalid user master from 180.166.184.66 port 49048 ssh2 |
2020-05-07 00:32:33 |
| 185.50.149.9 | attack | May 6 17:52:26 relay postfix/smtpd\[1606\]: warning: unknown\[185.50.149.9\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 May 6 17:52:46 relay postfix/smtpd\[3804\]: warning: unknown\[185.50.149.9\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 May 6 18:00:36 relay postfix/smtpd\[31974\]: warning: unknown\[185.50.149.9\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 May 6 18:00:58 relay postfix/smtpd\[1606\]: warning: unknown\[185.50.149.9\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 May 6 18:10:56 relay postfix/smtpd\[1606\]: warning: unknown\[185.50.149.9\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 ... |
2020-05-07 00:20:45 |