City: unknown
Region: unknown
Country: United States
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 13.57.225.85
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 32262
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;13.57.225.85. IN A
;; AUTHORITY SECTION:
. 305 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022022601 1800 900 604800 86400
;; Query time: 50 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 27 12:08:56 CST 2022
;; MSG SIZE rcvd: 105
85.225.57.13.in-addr.arpa domain name pointer ec2-13-57-225-85.us-west-1.compute.amazonaws.com.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
85.225.57.13.in-addr.arpa name = ec2-13-57-225-85.us-west-1.compute.amazonaws.com.
Authoritative answers can be found from:
| IP | Type | Details | Datetime |
|---|---|---|---|
| 106.0.6.236 | attack | Honeypot attack, port: 445, PTR: PTR record not found |
2020-09-05 14:18:35 |
| 185.225.136.37 | attackbotsspam | (From eric@talkwithwebvisitor.com) Hey, my name’s Eric and for just a second, imagine this… - Someone does a search and winds up at drlesliechiro.com. - They hang out for a minute to check it out. “I’m interested… but… maybe…” - And then they hit the back button and check out the other search results instead. - Bottom line – you got an eyeball, but nothing else to show for it. - There they go. This isn’t really your fault – it happens a LOT – studies show 7 out of 10 visitors to any site disappear without leaving a trace. But you CAN fix that. 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 lets you know right then and there – enabling you to call that lead while they’re literally looking over your site. CLICK HERE http://www.talkwithwebvisitors.com to try out a Live Demo with Talk With Web Visitor now to see exactly how it works. Time is money when it comes to connecting with leads – |
2020-09-05 14:28:33 |
| 191.234.178.249 | attackspam | (mod_security) mod_security (id:210492) triggered by 191.234.178.249 (BR/Brazil/-): 5 in the last 3600 secs |
2020-09-05 14:48:49 |
| 113.172.226.24 | attack | Honeypot attack, port: 5555, PTR: static.vnpt.vn. |
2020-09-05 14:40:47 |
| 78.28.233.52 | attackbots | Honeypot attack, port: 445, PTR: PTR record not found |
2020-09-05 14:26:14 |
| 122.164.242.113 | attackspambots | Sep 4 18:50:25 mellenthin postfix/smtpd[32087]: NOQUEUE: reject: RCPT from unknown[122.164.242.113]: 554 5.7.1 Service unavailable; Client host [122.164.242.113] blocked using zen.spamhaus.org; https://www.spamhaus.org/query/ip/122.164.242.113; from= |
2020-09-05 14:46:52 |
| 222.186.175.148 | attackspambots | Sep 5 03:53:13 firewall sshd[6153]: Failed password for root from 222.186.175.148 port 40560 ssh2 Sep 5 03:53:15 firewall sshd[6153]: Failed password for root from 222.186.175.148 port 40560 ssh2 Sep 5 03:53:19 firewall sshd[6153]: Failed password for root from 222.186.175.148 port 40560 ssh2 ... |
2020-09-05 14:53:48 |
| 220.76.205.178 | attack | Sep 4 18:13:59 sachi sshd\[19420\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=220.76.205.178 user=root Sep 4 18:14:01 sachi sshd\[19420\]: Failed password for root from 220.76.205.178 port 54205 ssh2 Sep 4 18:18:13 sachi sshd\[19706\]: Invalid user gavin from 220.76.205.178 Sep 4 18:18:13 sachi sshd\[19706\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=220.76.205.178 Sep 4 18:18:15 sachi sshd\[19706\]: Failed password for invalid user gavin from 220.76.205.178 port 55735 ssh2 |
2020-09-05 14:34:06 |
| 203.195.205.202 | attackbotsspam | Sep 5 04:03:53 mavik sshd[8844]: Invalid user postgres from 203.195.205.202 Sep 5 04:03:53 mavik sshd[8844]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.195.205.202 Sep 5 04:03:55 mavik sshd[8844]: Failed password for invalid user postgres from 203.195.205.202 port 43824 ssh2 Sep 5 04:08:39 mavik sshd[9130]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.195.205.202 user=root Sep 5 04:08:42 mavik sshd[9130]: Failed password for root from 203.195.205.202 port 36340 ssh2 ... |
2020-09-05 14:57:47 |
| 141.98.10.214 | attackbots | Sep 4 20:47:59 eddieflores sshd\[31047\]: Invalid user admin from 141.98.10.214 Sep 4 20:47:59 eddieflores sshd\[31047\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=141.98.10.214 Sep 4 20:48:01 eddieflores sshd\[31047\]: Failed password for invalid user admin from 141.98.10.214 port 38167 ssh2 Sep 4 20:48:33 eddieflores sshd\[31127\]: Invalid user admin from 141.98.10.214 Sep 4 20:48:33 eddieflores sshd\[31127\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=141.98.10.214 |
2020-09-05 14:52:37 |
| 159.65.155.255 | attack | Sep 5 00:19:27 ny01 sshd[6972]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.155.255 Sep 5 00:19:29 ny01 sshd[6972]: Failed password for invalid user tom from 159.65.155.255 port 50764 ssh2 Sep 5 00:23:23 ny01 sshd[7467]: Failed password for root from 159.65.155.255 port 48508 ssh2 |
2020-09-05 14:43:23 |
| 49.235.169.15 | attackspambots | 2020-09-05T05:47:12.235972vps1033 sshd[369]: Invalid user roy from 49.235.169.15 port 39284 2020-09-05T05:47:12.242758vps1033 sshd[369]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.169.15 2020-09-05T05:47:12.235972vps1033 sshd[369]: Invalid user roy from 49.235.169.15 port 39284 2020-09-05T05:47:14.793136vps1033 sshd[369]: Failed password for invalid user roy from 49.235.169.15 port 39284 ssh2 2020-09-05T05:51:20.015125vps1033 sshd[9043]: Invalid user ec2-user from 49.235.169.15 port 56124 ... |
2020-09-05 14:53:08 |
| 195.192.226.115 | attackbotsspam | firewall-block, port(s): 23/tcp |
2020-09-05 14:42:32 |
| 66.249.64.135 | attackbots | The IP has triggered Cloudflare WAF. CF-Ray: 5cd1f90fd8a409b0 | WAF_Rule_ID: 1bd9f7863d3d4d8faf68c16295216fb5 | WAF_Kind: firewall | CF_Action: allow | Country: US | CF_IPClass: searchEngine | Protocol: HTTP/1.1 | Method: GET | Host: www.wevg.org | User-Agent: Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html) | CF_DC: IAD. Report generated by Cloudflare-WAF-to-AbuseIPDB (https://github.com/SukkaW/Cloudflare-WAF-to-AbuseIPDB). |
2020-09-05 14:48:12 |
| 121.46.244.194 | attackbotsspam | Sep 5 07:32:29 mavik sshd[26723]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.46.244.194 Sep 5 07:32:31 mavik sshd[26723]: Failed password for invalid user maven from 121.46.244.194 port 28408 ssh2 Sep 5 07:35:58 mavik sshd[26926]: Invalid user odoo from 121.46.244.194 Sep 5 07:35:58 mavik sshd[26926]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.46.244.194 Sep 5 07:36:00 mavik sshd[26926]: Failed password for invalid user odoo from 121.46.244.194 port 48471 ssh2 ... |
2020-09-05 14:38:24 |