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 <<>> 57.48.91.38
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 52172
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;57.48.91.38. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025012902 1800 900 604800 86400
;; Query time: 38 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Jan 30 13:44:43 CST 2025
;; MSG SIZE rcvd: 104Host 38.91.48.57.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 38.91.48.57.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 198.20.180.70 | attack | (From cath@send.kathreadwrites.net) Hello I wanted to share a quick ranking case study with you (I'm a copywriter and onpage SEO expert). Google Loves the RIGHT WORDS in the RIGHT PLACE. I Got It Wrong. I changed 8 words on a page...and you won't believe what happened. So I wrote a case study about it. Read it here: https://kathreadwrites.net/onpage-us/ ? Put the WRONG WORDS in the WRONG PLACE and you will not rank. PERIOD. I hope this case study inspires you to check out your own on-page optimization. Be Amazing Cath P.S. To get in touch, please use the contact form on my website instead of emailing me. Unsubscribe |
2019-07-23 04:48:26 |
| 59.124.154.223 | attackspambots | Unauthorized connection attempt from IP address 59.124.154.223 on Port 445(SMB) |
2019-07-23 04:57:01 |
| 118.165.99.154 | attackbotsspam | Honeypot attack, port: 23, PTR: 118-165-99-154.dynamic-ip.hinet.net. |
2019-07-23 05:07:09 |
| 2.101.57.193 | attack | Honeypot attack, port: 5555, PTR: host-2-101-57-193.as13285.net. |
2019-07-23 05:05:11 |
| 37.252.190.224 | attackspambots | Jul 22 15:40:31 dedicated sshd[7687]: Invalid user hc from 37.252.190.224 port 47212 |
2019-07-23 04:33:23 |
| 134.90.149.146 | attackbotsspam | Spam-Mail via Contact-Form 22.07.2019 / 20:46 IP-Adresse | 134.90.149.146 |
2019-07-23 05:10:57 |
| 59.148.43.97 | attackspam | Jul 23 00:44:34 itv-usvr-02 sshd[1361]: Invalid user admin from 59.148.43.97 port 35588 Jul 23 00:44:34 itv-usvr-02 sshd[1361]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=59.148.43.97 Jul 23 00:44:34 itv-usvr-02 sshd[1361]: Invalid user admin from 59.148.43.97 port 35588 Jul 23 00:44:36 itv-usvr-02 sshd[1361]: Failed password for invalid user admin from 59.148.43.97 port 35588 ssh2 Jul 23 00:44:34 itv-usvr-02 sshd[1361]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=59.148.43.97 Jul 23 00:44:34 itv-usvr-02 sshd[1361]: Invalid user admin from 59.148.43.97 port 35588 Jul 23 00:44:36 itv-usvr-02 sshd[1361]: Failed password for invalid user admin from 59.148.43.97 port 35588 ssh2 Jul 23 00:44:37 itv-usvr-02 sshd[1361]: Failed password for invalid user admin from 59.148.43.97 port 35588 ssh2 |
2019-07-23 05:13:42 |
| 178.32.141.39 | attackspambots | Jul 22 09:44:15 plusreed sshd[25769]: Invalid user pokemon from 178.32.141.39 ... |
2019-07-23 05:17:26 |
| 179.108.105.126 | attack | Jul 22 17:34:00 Proxmox sshd\[6894\]: Invalid user ra from 179.108.105.126 port 37048 Jul 22 17:34:00 Proxmox sshd\[6894\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=179.108.105.126 Jul 22 17:34:02 Proxmox sshd\[6894\]: Failed password for invalid user ra from 179.108.105.126 port 37048 ssh2 Jul 22 17:46:38 Proxmox sshd\[20334\]: Invalid user techadmin from 179.108.105.126 port 60436 Jul 22 17:46:38 Proxmox sshd\[20334\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=179.108.105.126 Jul 22 17:46:40 Proxmox sshd\[20334\]: Failed password for invalid user techadmin from 179.108.105.126 port 60436 ssh2 |
2019-07-23 04:56:30 |
| 46.173.61.71 | attackbots | Honeypot attack, port: 445, PTR: 46-173-61-71.gorcom.ru. |
2019-07-23 05:09:13 |
| 91.51.179.115 | attack | Jul 22 14:36:37 nxxxxxxx sshd[14320]: Invalid user carmen from 91.51.179.115 Jul 22 14:36:40 nxxxxxxx sshd[14320]: Failed password for invalid user carmen from 91.51.179.115 port 60290 ssh2 Jul 22 14:45:23 nxxxxxxx sshd[15425]: Invalid user fotos from 91.51.179.115 ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=91.51.179.115 |
2019-07-23 05:13:27 |
| 103.52.16.35 | attack | Jul 22 16:17:35 icinga sshd[5298]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.52.16.35 Jul 22 16:17:37 icinga sshd[5298]: Failed password for invalid user omc from 103.52.16.35 port 52350 ssh2 ... |
2019-07-23 04:40:06 |
| 84.191.215.70 | attackbotsspam | Invalid user pi from 84.191.215.70 port 42284 Invalid user pi from 84.191.215.70 port 42288 pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=84.191.215.70 pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=84.191.215.70 Failed password for invalid user pi from 84.191.215.70 port 42284 ssh2 |
2019-07-23 04:39:51 |
| 154.120.225.134 | attack | Jul 22 16:39:06 unicornsoft sshd\[20379\]: Invalid user bdoherty from 154.120.225.134 Jul 22 16:39:06 unicornsoft sshd\[20379\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=154.120.225.134 Jul 22 16:39:08 unicornsoft sshd\[20379\]: Failed password for invalid user bdoherty from 154.120.225.134 port 40906 ssh2 |
2019-07-23 05:17:12 |
| 79.8.245.19 | attackspambots | 2019-07-22T20:12:42.715079enmeeting.mahidol.ac.th sshd\[26597\]: Invalid user pierre from 79.8.245.19 port 49837 2019-07-22T20:12:42.729759enmeeting.mahidol.ac.th sshd\[26597\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=79.8.245.19 2019-07-22T20:12:45.063696enmeeting.mahidol.ac.th sshd\[26597\]: Failed password for invalid user pierre from 79.8.245.19 port 49837 ssh2 ... |
2019-07-23 04:34:39 |