City: Zürich
Region: Zurich
Country: Switzerland
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 51.96.216.89
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 60053
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;51.96.216.89. IN A
;; AUTHORITY SECTION:
. 503 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2024052803 1800 900 604800 86400
;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed May 29 10:17:05 CST 2024
;; MSG SIZE rcvd: 10589.216.96.51.in-addr.arpa domain name pointer ec2-51-96-216-89.eu-central-2.compute.amazonaws.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
89.216.96.51.in-addr.arpa name = ec2-51-96-216-89.eu-central-2.compute.amazonaws.com.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 59.127.95.214 | attackspambots | [N10.H2.VM2] Port Scanner Detected Blocked by UFW |
2020-08-11 05:13:32 |
| 216.218.206.84 | attack | srv02 Mass scanning activity detected Target: 11211 .. |
2020-08-11 05:33:39 |
| 106.12.210.77 | attackspambots | 2020-08-10T22:30:42.242281+02:00 |
2020-08-11 05:38:04 |
| 195.158.26.238 | attackbots | Aug 10 22:29:16 pve1 sshd[5385]: Failed password for root from 195.158.26.238 port 59116 ssh2 ... |
2020-08-11 05:08:27 |
| 89.187.172.220 | attackbotsspam | Brute forcing email accounts |
2020-08-11 05:17:47 |
| 123.185.16.214 | attackspam | Unauthorized connection attempt from IP address 123.185.16.214 on Port 445(SMB) |
2020-08-11 05:19:01 |
| 211.170.61.184 | attackspam | (sshd) Failed SSH login from 211.170.61.184 (KR/South Korea/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Aug 10 22:12:37 amsweb01 sshd[7154]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.170.61.184 user=root Aug 10 22:12:39 amsweb01 sshd[7154]: Failed password for root from 211.170.61.184 port 34856 ssh2 Aug 10 22:26:50 amsweb01 sshd[9529]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.170.61.184 user=root Aug 10 22:26:51 amsweb01 sshd[9529]: Failed password for root from 211.170.61.184 port 62894 ssh2 Aug 10 22:30:56 amsweb01 sshd[10080]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.170.61.184 user=root |
2020-08-11 05:41:19 |
| 178.62.187.136 | attackbotsspam | 2020-08-10T20:47:22.253912shield sshd\[15019\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.62.187.136 user=root 2020-08-10T20:47:24.175525shield sshd\[15019\]: Failed password for root from 178.62.187.136 port 40456 ssh2 2020-08-10T20:52:05.043739shield sshd\[15573\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.62.187.136 user=root 2020-08-10T20:52:07.010700shield sshd\[15573\]: Failed password for root from 178.62.187.136 port 50988 ssh2 2020-08-10T20:56:55.909513shield sshd\[15955\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.62.187.136 user=root |
2020-08-11 05:12:27 |
| 192.200.215.91 | attackbotsspam | WordPress vulnerability sniffing (looking for /wp-content/plugins/videowhisper-video-presentation/vp/translation.php) |
2020-08-11 05:31:19 |
| 23.95.97.227 | attackbotsspam | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found mcfaddenchiropractic.com after doing a quick search – you showed up near the top of the rankings, so whatever you’re doing for SEO, looks like it’s working well. So here’s my question – what happens AFTER someone lands on your site? Anything? Research tells us at least 70% of the people who find your site, after a quick once-over, they disappear… forever. That means that all the work and effort you put into getting them to show up, goes down the tubes. Why would you want all that good work – and the great site you’ve built – go to waste? Because the odds are they’ll just skip over calling or even grabbing their phone, leaving you high and dry. But here’s a thought… what if you could make it super-simple for someone to raise their hand, say, “okay, let’s talk” without requiring them to even pull their cell phone from their pocket? You can – thanks to revolutionary new softwar |
2020-08-11 05:18:05 |
| 177.54.128.90 | attack | Unauthorized connection attempt from IP address 177.54.128.90 on Port 445(SMB) |
2020-08-11 05:40:31 |
| 222.186.175.150 | attackspambots | Aug 10 23:01:40 nextcloud sshd\[3833\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.150 user=root Aug 10 23:01:43 nextcloud sshd\[3833\]: Failed password for root from 222.186.175.150 port 20000 ssh2 Aug 10 23:02:07 nextcloud sshd\[4551\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.150 user=root |
2020-08-11 05:04:48 |
| 114.231.8.109 | attackbots | Aug 11 08:30:52 pmg postfix/postscreen[1258]: PREGREET 17 after 2.2 from [114.231.8.109]:1462: EHLO YQe7h9HaRu Aug 11 08:31:13 pmg postfix/postscreen[1258]: PREGREET 15 after 2.2 from [114.231.8.109]:4603: EHLO LDS0j ... |
2020-08-11 05:21:21 |
| 211.72.212.241 | attack | Unauthorized connection attempt from IP address 211.72.212.241 on Port 445(SMB) |
2020-08-11 05:23:58 |
| 210.212.29.215 | attackbotsspam | Aug 10 22:43:40 eventyay sshd[19816]: Failed password for root from 210.212.29.215 port 53706 ssh2 Aug 10 22:46:46 eventyay sshd[19902]: Failed password for root from 210.212.29.215 port 39480 ssh2 ... |
2020-08-11 05:04:12 |