City: unknown
Region: unknown
Country: None
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 104.78.86.59
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 18404
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;104.78.86.59. IN A
;; AUTHORITY SECTION:
. 378 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2020050800 1800 900 604800 86400
;; Query time: 55 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri May 08 19:32:33 CST 2020
;; MSG SIZE rcvd: 11659.86.78.104.in-addr.arpa domain name pointer a104-78-86-59.deploy.static.akamaitechnologies.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
59.86.78.104.in-addr.arpa name = a104-78-86-59.deploy.static.akamaitechnologies.com.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 200.110.174.137 | attackbotsspam | Feb 3 20:04:29 sd-53420 sshd\[22786\]: Invalid user tun from 200.110.174.137 Feb 3 20:04:29 sd-53420 sshd\[22786\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.110.174.137 Feb 3 20:04:32 sd-53420 sshd\[22786\]: Failed password for invalid user tun from 200.110.174.137 port 52960 ssh2 Feb 3 20:07:45 sd-53420 sshd\[23065\]: Invalid user owa2 from 200.110.174.137 Feb 3 20:07:45 sd-53420 sshd\[23065\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.110.174.137 ... |
2020-02-04 03:17:02 |
| 14.186.55.66 | attackspam | Unauthorized connection attempt detected from IP address 14.186.55.66 to port 22 [J] |
2020-02-04 03:36:48 |
| 45.79.114.194 | attackbotsspam | Unauthorized connection attempt detected from IP address 45.79.114.194 to port 789 [J] |
2020-02-04 03:34:41 |
| 170.106.36.31 | attackbotsspam | Unauthorized connection attempt detected from IP address 170.106.36.31 to port 505 [J] |
2020-02-04 03:44:28 |
| 123.20.176.23 | attackbots | Unauthorized connection attempt detected from IP address 123.20.176.23 to port 22 [J] |
2020-02-04 03:47:28 |
| 188.15.191.2 | attack | Unauthorized connection attempt detected from IP address 188.15.191.2 to port 2220 [J] |
2020-02-04 03:42:20 |
| 114.34.189.5 | attackbotsspam | Unauthorized connection attempt detected from IP address 114.34.189.5 to port 81 [J] |
2020-02-04 03:26:58 |
| 106.54.138.147 | attack | Unauthorized connection attempt detected from IP address 106.54.138.147 to port 80 [J] |
2020-02-04 03:27:52 |
| 125.197.104.59 | attackspambots | Unauthorized connection attempt detected from IP address 125.197.104.59 to port 23 [J] |
2020-02-04 03:24:39 |
| 117.50.6.201 | attackbots | Unauthorized connection attempt detected from IP address 117.50.6.201 to port 995 [J] |
2020-02-04 03:26:34 |
| 122.117.43.178 | attackspambots | Unauthorized connection attempt detected from IP address 122.117.43.178 to port 81 [J] |
2020-02-04 03:24:57 |
| 49.233.139.79 | attackspambots | Unauthorized connection attempt detected from IP address 49.233.139.79 to port 2220 [J] |
2020-02-04 03:33:14 |
| 118.24.54.178 | attackspam | Automatic report - Banned IP Access |
2020-02-04 03:50:06 |
| 128.1.138.97 | attackspam | Unauthorized connection attempt detected from IP address 128.1.138.97 to port 2220 [J] |
2020-02-04 03:24:12 |
| 190.186.47.224 | attackspam | Unauthorized connection attempt detected from IP address 190.186.47.224 to port 23 [J] |
2020-02-04 03:41:33 |