City: Washington
Region: District of Columbia
Country: United States
Internet Service Provider: AT&T
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 12.246.39.108
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 40257
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;12.246.39.108. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025030201 1800 900 604800 86400
;; Query time: 9 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Mar 03 08:29:53 CST 2025
;; MSG SIZE rcvd: 106Host 108.39.246.12.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 108.39.246.12.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 114.112.58.134 | attackspambots | Unauthorized SSH login attempts |
2019-12-24 03:43:48 |
| 124.105.25.33 | attackspambots | Fail2Ban Ban Triggered |
2019-12-24 04:05:48 |
| 172.105.70.230 | attackspam | Dec 23 20:58:25 vpn01 sshd[20933]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=172.105.70.230 Dec 23 20:58:27 vpn01 sshd[20933]: Failed password for invalid user bt1944server from 172.105.70.230 port 56998 ssh2 ... |
2019-12-24 04:00:58 |
| 187.87.17.89 | attack | 2323/tcp 23/tcp... [2019-10-25/12-22]7pkt,2pt.(tcp) |
2019-12-24 04:12:21 |
| 129.204.37.181 | attackbotsspam | Dec 5 17:24:39 yesfletchmain sshd\[21919\]: User root from 129.204.37.181 not allowed because not listed in AllowUsers Dec 5 17:24:39 yesfletchmain sshd\[21919\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.37.181 user=root Dec 5 17:24:41 yesfletchmain sshd\[21919\]: Failed password for invalid user root from 129.204.37.181 port 62872 ssh2 Dec 5 17:32:26 yesfletchmain sshd\[22081\]: User root from 129.204.37.181 not allowed because not listed in AllowUsers Dec 5 17:32:27 yesfletchmain sshd\[22081\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.37.181 user=root ... |
2019-12-24 03:44:51 |
| 42.117.54.61 | attackspambots | Unauthorized connection attempt detected from IP address 42.117.54.61 to port 445 |
2019-12-24 03:45:52 |
| 92.222.84.34 | attack | Dec 23 12:57:13 firewall sshd[14339]: Failed password for invalid user guest from 92.222.84.34 port 47768 ssh2 Dec 23 13:02:47 firewall sshd[14456]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=92.222.84.34 user=root Dec 23 13:02:50 firewall sshd[14456]: Failed password for root from 92.222.84.34 port 53492 ssh2 ... |
2019-12-24 03:56:55 |
| 129.204.205.171 | attackspam | Sep 29 15:57:53 yesfletchmain sshd\[29391\]: Invalid user schedule from 129.204.205.171 port 59902 Sep 29 15:57:53 yesfletchmain sshd\[29391\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.205.171 Sep 29 15:57:55 yesfletchmain sshd\[29391\]: Failed password for invalid user schedule from 129.204.205.171 port 59902 ssh2 Sep 29 16:02:32 yesfletchmain sshd\[29548\]: Invalid user zabbix from 129.204.205.171 port 50926 Sep 29 16:02:32 yesfletchmain sshd\[29548\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.205.171 ... |
2019-12-24 04:01:44 |
| 170.80.49.2 | attackspam | 1433/tcp 445/tcp... [2019-10-23/12-22]16pkt,2pt.(tcp) |
2019-12-24 04:03:55 |
| 129.204.217.65 | attackspambots | Jun 15 20:36:48 yesfletchmain sshd\[20634\]: Invalid user tom from 129.204.217.65 port 36226 Jun 15 20:36:48 yesfletchmain sshd\[20634\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.217.65 Jun 15 20:36:50 yesfletchmain sshd\[20634\]: Failed password for invalid user tom from 129.204.217.65 port 36226 ssh2 Jun 15 20:40:31 yesfletchmain sshd\[20848\]: User root from 129.204.217.65 not allowed because not listed in AllowUsers Jun 15 20:40:31 yesfletchmain sshd\[20848\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.217.65 user=root ... |
2019-12-24 03:57:56 |
| 112.220.85.26 | attackbots | Dec 23 16:36:08 lnxweb61 sshd[7349]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.220.85.26 |
2019-12-24 04:19:30 |
| 129.204.210.237 | attackspam | Apr 24 10:29:28 yesfletchmain sshd\[19541\]: Invalid user sentry from 129.204.210.237 port 56464 Apr 24 10:29:28 yesfletchmain sshd\[19541\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.210.237 Apr 24 10:29:30 yesfletchmain sshd\[19541\]: Failed password for invalid user sentry from 129.204.210.237 port 56464 ssh2 Apr 24 10:32:11 yesfletchmain sshd\[19597\]: Invalid user amssys from 129.204.210.237 port 53262 Apr 24 10:32:11 yesfletchmain sshd\[19597\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.210.237 ... |
2019-12-24 03:59:19 |
| 117.34.118.44 | attack | 12/23/2019-20:15:54.286046 117.34.118.44 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433 |
2019-12-24 04:09:10 |
| 129.204.3.8 | attackspam | May 22 17:59:14 yesfletchmain sshd\[24288\]: Invalid user ux from 129.204.3.8 port 33786 May 22 17:59:14 yesfletchmain sshd\[24288\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.3.8 May 22 17:59:16 yesfletchmain sshd\[24288\]: Failed password for invalid user ux from 129.204.3.8 port 33786 ssh2 May 22 18:04:38 yesfletchmain sshd\[24393\]: Invalid user sun from 129.204.3.8 port 45772 May 22 18:04:38 yesfletchmain sshd\[24393\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.3.8 ... |
2019-12-24 03:47:42 |
| 103.238.213.158 | attack | 3389/tcp 3389/tcp 3389/tcp [2019-12-18/22]3pkt |
2019-12-24 04:06:11 |