城市(city): unknown
省份(region): unknown
国家(country): United States
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 13.234.144.83
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 39036
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;13.234.144.83. IN A
;; AUTHORITY SECTION:
. 511 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022022601 1800 900 604800 86400
;; Query time: 84 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 27 12:01:30 CST 2022
;; MSG SIZE rcvd: 10683.144.234.13.in-addr.arpa domain name pointer ec2-13-234-144-83.ap-south-1.compute.amazonaws.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
83.144.234.13.in-addr.arpa name = ec2-13-234-144-83.ap-south-1.compute.amazonaws.com.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 182.255.42.116 | attack | Automatic report - XMLRPC Attack |
2020-04-22 20:50:49 |
| 75.127.5.72 | attackspambots | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found millenniumchiro.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 software tha |
2020-04-22 20:48:41 |
| 198.49.73.13 | attack | Apr 22 12:04:58 scw-6657dc sshd[8147]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=198.49.73.13 Apr 22 12:04:58 scw-6657dc sshd[8147]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=198.49.73.13 Apr 22 12:05:00 scw-6657dc sshd[8147]: Failed password for invalid user lt from 198.49.73.13 port 60966 ssh2 ... |
2020-04-22 20:29:17 |
| 68.116.41.6 | attack | no |
2020-04-22 20:36:00 |
| 94.177.217.21 | attack | Apr 22 08:48:59 CT721 sshd[10287]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.177.217.21 user=r.r Apr 22 08:49:01 CT721 sshd[10287]: Failed password for r.r from 94.177.217.21 port 37648 ssh2 Apr 22 08:49:01 CT721 sshd[10287]: Received disconnect from 94.177.217.21 port 37648:11: Bye Bye [preauth] Apr 22 08:49:01 CT721 sshd[10287]: Disconnected from 94.177.217.21 port 37648 [preauth] Apr 22 08:57:49 CT721 sshd[10500]: Invalid user nd from 94.177.217.21 port 53888 Apr 22 08:57:49 CT721 sshd[10500]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.177.217.21 Apr 22 08:57:51 CT721 sshd[10500]: Failed password for invalid user nd from 94.177.217.21 port 53888 ssh2 Apr 22 08:57:51 CT721 sshd[10500]: Received disconnect from 94.177.217.21 port 53888:11: Bye Bye [preauth] Apr 22 08:57:51 CT721 sshd[10500]: Disconnected from 94.177.217.21 port 53888 [preauth] ........ ----------------------------------------------- https://ww |
2020-04-22 20:30:24 |
| 69.203.144.38 | attackspam | Honeypot attack, port: 5555, PTR: cpe-69-203-144-38.nyc.res.rr.com. |
2020-04-22 20:34:44 |
| 177.23.184.99 | attackbotsspam | Apr 22 08:31:04 ny01 sshd[1954]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.23.184.99 Apr 22 08:31:06 ny01 sshd[1954]: Failed password for invalid user oa from 177.23.184.99 port 33862 ssh2 Apr 22 08:36:21 ny01 sshd[2536]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.23.184.99 |
2020-04-22 20:38:34 |
| 222.186.30.35 | attack | 22.04.2020 12:52:06 SSH access blocked by firewall |
2020-04-22 20:58:03 |
| 203.160.58.194 | attackspambots | Sending SPAM email |
2020-04-22 20:20:38 |
| 41.204.77.142 | attackbotsspam | Honeypot attack, port: 445, PTR: PTR record not found |
2020-04-22 20:25:20 |
| 113.193.243.35 | attackbotsspam | $f2bV_matches |
2020-04-22 20:59:45 |
| 103.66.232.47 | attackspam | scan r |
2020-04-22 20:46:58 |
| 114.230.202.232 | attackbots | Apr 22 07:57:24 NPSTNNYC01T sshd[6540]: Failed password for root from 114.230.202.232 port 58652 ssh2 Apr 22 08:01:55 NPSTNNYC01T sshd[6928]: Failed password for root from 114.230.202.232 port 40180 ssh2 Apr 22 08:05:12 NPSTNNYC01T sshd[7178]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.230.202.232 ... |
2020-04-22 20:18:33 |
| 91.134.248.245 | attack | $f2bV_matches |
2020-04-22 20:24:58 |
| 36.110.217.140 | attack | Apr 22 14:27:18 plex sshd[24412]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=36.110.217.140 user=root Apr 22 14:27:20 plex sshd[24412]: Failed password for root from 36.110.217.140 port 42680 ssh2 |
2020-04-22 20:49:35 |