城市(city): unknown
省份(region): unknown
国家(country): United States
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 214.132.15.212
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9681
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;214.132.15.212. IN A
;; AUTHORITY SECTION:
. 29 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025021902 1800 900 604800 86400
;; Query time: 16 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 20 12:29:06 CST 2025
;; MSG SIZE rcvd: 107Host 212.15.132.214.in-addr.arpa. not found: 3(NXDOMAIN)
server can't find 214.132.15.212.in-addr.arpa: SERVFAIL| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 182.72.31.173 | attackspam | 20/1/23@19:16:28: FAIL: Alarm-Network address from=182.72.31.173 ... |
2020-01-24 09:47:23 |
| 111.231.141.221 | attackbots | Unauthorized connection attempt detected from IP address 111.231.141.221 to port 2220 [J] |
2020-01-24 09:54:09 |
| 104.140.83.156 | attack | (From eric@talkwithcustomer.com) Hi, Let’s take a quick trip to Tomorrow-land. I’m not talking about a theme park, I’m talking about your business’s future… Don’t worry, we won’t even need a crystal ball. Just imagine… … a future where the money you invest in driving traffic to your site denvertechchiro.com pays off with tons of calls from qualified leads. And the difference between what you experienced in the past is staggering – you’re seeing 10X, 20X, 50X, even up to a 100X more leads coming from your website denvertechchiro.com. Leads that are already engaged with what you have to offer and are ready to learn more and even open their wallets. Seeing all this taking place in your business, you think back: What did I do only a short time ago that made such a huge difference? And then it hits you: You took advantage of a free 14 day Test Drive of TalkWithCustomer. You installed TalkWithCustomer on denvertechchiro.com – it was a snap. And practically overnight customers st |
2020-01-24 13:01:31 |
| 80.82.70.106 | attack | Jan 24 02:31:49 debian-2gb-nbg1-2 kernel: \[2088786.544122\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=80.82.70.106 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=50586 PROTO=TCP SPT=56629 DPT=41312 WINDOW=1024 RES=0x00 SYN URGP=0 |
2020-01-24 09:37:29 |
| 36.91.37.253 | attackbots | Unauthorized connection attempt from IP address 36.91.37.253 on Port 445(SMB) |
2020-01-24 09:43:30 |
| 112.64.34.165 | attack | Jan 24 03:44:21 pkdns2 sshd\[10729\]: Invalid user fg from 112.64.34.165Jan 24 03:44:24 pkdns2 sshd\[10729\]: Failed password for invalid user fg from 112.64.34.165 port 58807 ssh2Jan 24 03:47:36 pkdns2 sshd\[10954\]: Invalid user account from 112.64.34.165Jan 24 03:47:38 pkdns2 sshd\[10954\]: Failed password for invalid user account from 112.64.34.165 port 42022 ssh2Jan 24 03:50:51 pkdns2 sshd\[11196\]: Invalid user cos from 112.64.34.165Jan 24 03:50:53 pkdns2 sshd\[11196\]: Failed password for invalid user cos from 112.64.34.165 port 53471 ssh2 ... |
2020-01-24 09:53:07 |
| 42.118.91.119 | attackbotsspam | Unauthorized connection attempt from IP address 42.118.91.119 on Port 445(SMB) |
2020-01-24 09:29:51 |
| 177.154.32.137 | attackspam | Unauthorized connection attempt detected from IP address 177.154.32.137 to port 23 [J] |
2020-01-24 09:55:06 |
| 129.211.30.94 | attack | Jan 24 01:16:21 mout sshd[24885]: Invalid user five from 129.211.30.94 port 49644 |
2020-01-24 09:52:15 |
| 46.38.144.102 | attackspam | Jan 24 02:31:56 lnxmail61 postfix/smtpd[30225]: warning: unknown[46.38.144.102]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 |
2020-01-24 09:33:36 |
| 218.248.18.211 | attackbots | Unauthorized connection attempt from IP address 218.248.18.211 on Port 445(SMB) |
2020-01-24 09:46:11 |
| 152.136.203.208 | attackbots | SSH invalid-user multiple login try |
2020-01-24 09:40:55 |
| 218.92.0.175 | attackspam | Jan 23 18:56:00 sachi sshd\[30027\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.175 user=root Jan 23 18:56:02 sachi sshd\[30027\]: Failed password for root from 218.92.0.175 port 41212 ssh2 Jan 23 18:56:21 sachi sshd\[30052\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.175 user=root Jan 23 18:56:23 sachi sshd\[30052\]: Failed password for root from 218.92.0.175 port 8288 ssh2 Jan 23 18:56:35 sachi sshd\[30052\]: Failed password for root from 218.92.0.175 port 8288 ssh2 |
2020-01-24 13:02:51 |
| 139.159.44.150 | attackspam | Unauthorized connection attempt from IP address 139.159.44.150 on Port 445(SMB) |
2020-01-24 09:39:36 |
| 51.77.144.50 | attack | Jan 24 05:58:17 [host] sshd[32192]: Invalid user prueba from 51.77.144.50 Jan 24 05:58:17 [host] sshd[32192]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.77.144.50 Jan 24 05:58:19 [host] sshd[32192]: Failed password for invalid user prueba from 51.77.144.50 port 32858 ssh2 |
2020-01-24 13:10:55 |