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 <<>> 104.106.40.52
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 45672
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;104.106.40.52. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025020401 1800 900 604800 86400
;; Query time: 35 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Feb 05 13:38:43 CST 2025
;; MSG SIZE rcvd: 10652.40.106.104.in-addr.arpa domain name pointer a104-106-40-52.deploy.static.akamaitechnologies.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
52.40.106.104.in-addr.arpa name = a104-106-40-52.deploy.static.akamaitechnologies.com.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 183.88.234.22 | attackspam | 'IP reached maximum auth failures for a one day block' |
2020-04-26 03:19:13 |
| 80.211.245.103 | attackspambots | Apr 25 16:10:41 pkdns2 sshd\[29223\]: Invalid user ams from 80.211.245.103Apr 25 16:10:43 pkdns2 sshd\[29223\]: Failed password for invalid user ams from 80.211.245.103 port 48518 ssh2Apr 25 16:15:15 pkdns2 sshd\[29423\]: Invalid user qqq from 80.211.245.103Apr 25 16:15:16 pkdns2 sshd\[29423\]: Failed password for invalid user qqq from 80.211.245.103 port 60922 ssh2Apr 25 16:19:47 pkdns2 sshd\[29566\]: Invalid user nice from 80.211.245.103Apr 25 16:19:49 pkdns2 sshd\[29566\]: Failed password for invalid user nice from 80.211.245.103 port 45096 ssh2 ... |
2020-04-26 03:24:17 |
| 191.102.156.98 | attackspam | (From eric@talkwithwebvisitor.com) Hey, this is Eric and I ran across rasselfamilychiropractic.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 htt |
2020-04-26 03:31:58 |
| 198.46.81.43 | attack | xmlrpc attack |
2020-04-26 03:11:03 |
| 157.230.251.100 | attack | $f2bV_matches |
2020-04-26 03:05:37 |
| 157.230.41.212 | attack | $f2bV_matches |
2020-04-26 03:09:00 |
| 141.226.12.5 | attackspambots | bruteforce detected |
2020-04-26 03:02:29 |
| 221.217.227.86 | attackbots | 2020-04-25T17:40:42.389481amanda2.illicoweb.com sshd\[44109\]: Invalid user app from 221.217.227.86 port 23713 2020-04-25T17:40:42.394593amanda2.illicoweb.com sshd\[44109\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.217.227.86 2020-04-25T17:40:44.287299amanda2.illicoweb.com sshd\[44109\]: Failed password for invalid user app from 221.217.227.86 port 23713 ssh2 2020-04-25T17:44:29.011241amanda2.illicoweb.com sshd\[44272\]: Invalid user newadmin from 221.217.227.86 port 58625 2020-04-25T17:44:29.017873amanda2.illicoweb.com sshd\[44272\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.217.227.86 ... |
2020-04-26 03:30:34 |
| 183.245.99.59 | attackbots | Invalid user testftp from 183.245.99.59 port 43362 |
2020-04-26 03:25:15 |
| 31.13.127.19 | attack | Unauthorized connection attempt, very violent continuous attack! IP address disabled! |
2020-04-26 03:22:41 |
| 123.206.111.27 | attackspambots | Apr 25 10:14:32 firewall sshd[4856]: Invalid user cimeq from 123.206.111.27 Apr 25 10:14:34 firewall sshd[4856]: Failed password for invalid user cimeq from 123.206.111.27 port 41496 ssh2 Apr 25 10:20:17 firewall sshd[4992]: Invalid user git from 123.206.111.27 ... |
2020-04-26 03:22:54 |
| 222.186.31.166 | attackbots | 2020-04-25T21:13:47.853257vps773228.ovh.net sshd[18591]: Failed password for root from 222.186.31.166 port 27961 ssh2 2020-04-25T21:13:49.941981vps773228.ovh.net sshd[18591]: Failed password for root from 222.186.31.166 port 27961 ssh2 2020-04-25T21:13:51.958937vps773228.ovh.net sshd[18591]: Failed password for root from 222.186.31.166 port 27961 ssh2 2020-04-25T21:13:53.915146vps773228.ovh.net sshd[18593]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.31.166 user=root 2020-04-25T21:13:55.791446vps773228.ovh.net sshd[18593]: Failed password for root from 222.186.31.166 port 58296 ssh2 ... |
2020-04-26 03:14:08 |
| 222.186.175.151 | attackbots | Apr 25 20:43:08 vps sshd[402178]: Failed password for root from 222.186.175.151 port 54952 ssh2 Apr 25 20:43:11 vps sshd[402178]: Failed password for root from 222.186.175.151 port 54952 ssh2 Apr 25 20:43:14 vps sshd[402178]: Failed password for root from 222.186.175.151 port 54952 ssh2 Apr 25 20:43:17 vps sshd[402178]: Failed password for root from 222.186.175.151 port 54952 ssh2 Apr 25 20:43:21 vps sshd[402178]: Failed password for root from 222.186.175.151 port 54952 ssh2 ... |
2020-04-26 02:59:46 |
| 188.234.151.23 | attackbots | TCP src-port=39241 dst-port=25 Listed on dnsbl-sorbs abuseat-org barracuda (Project Honey Pot rated Suspicious) (247) |
2020-04-26 03:16:28 |
| 222.186.15.62 | attack | 25.04.2020 18:59:16 SSH access blocked by firewall |
2020-04-26 03:12:15 |