城市(city): unknown
省份(region): unknown
国家(country): Viet Nam
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 14.254.197.73
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9844
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;14.254.197.73. IN A
;; AUTHORITY SECTION:
. 600 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022020700 1800 900 604800 86400
;; Query time: 53 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 07 14:58:44 CST 2022
;; MSG SIZE rcvd: 10673.197.254.14.in-addr.arpa domain name pointer static.vnpt.vn.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
73.197.254.14.in-addr.arpa name = static.vnpt.vn.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 64.94.208.204 | attack | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found drjenniferbrandon.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 t |
2020-03-05 00:03:40 |
| 58.225.75.147 | attack | " " |
2020-03-05 00:13:06 |
| 221.122.67.66 | attack | $f2bV_matches |
2020-03-05 00:23:07 |
| 191.253.36.114 | attack | 5555/tcp [2020-03-04]1pkt |
2020-03-05 00:44:28 |
| 221.13.51.91 | attack | $f2bV_matches |
2020-03-05 00:08:40 |
| 41.208.70.187 | attackbotsspam | Honeypot attack, port: 445, PTR: 41.208.70.187.static.ltt.ly. |
2020-03-05 00:34:13 |
| 221.12.100.170 | attackbotsspam | $f2bV_matches |
2020-03-05 00:40:47 |
| 221.122.92.59 | attack | $f2bV_matches |
2020-03-05 00:18:31 |
| 3.1.213.253 | attackbotsspam | 9200/tcp [2020-03-04]1pkt |
2020-03-05 00:08:08 |
| 200.41.98.6 | attackbots | Honeypot attack, port: 445, PTR: PTR record not found |
2020-03-05 00:20:44 |
| 52.142.160.188 | attackbots | Lines containing failures of 52.142.160.188 Mar 2 14:57:55 mellenthin sshd[26167]: Invalid user alteseisen from 52.142.160.188 port 38388 Mar 2 14:57:55 mellenthin sshd[26167]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=52.142.160.188 Mar 2 14:57:57 mellenthin sshd[26167]: Failed password for invalid user alteseisen from 52.142.160.188 port 38388 ssh2 Mar 2 14:57:57 mellenthin sshd[26167]: Received disconnect from 52.142.160.188 port 38388:11: Normal Shutdown [preauth] Mar 2 14:57:57 mellenthin sshd[26167]: Disconnected from invalid user alteseisen 52.142.160.188 port 38388 [preauth] Mar 2 15:06:02 mellenthin sshd[31583]: Invalid user alteseisen from 52.142.160.188 port 36128 Mar 2 15:06:02 mellenthin sshd[31583]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=52.142.160.188 ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=52.142.160.188 |
2020-03-05 00:46:16 |
| 221.12.107.26 | attackspambots | $f2bV_matches |
2020-03-05 00:39:29 |
| 120.70.100.89 | attack | Mar 4 19:37:03 gw1 sshd[15240]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=120.70.100.89 Mar 4 19:37:05 gw1 sshd[15240]: Failed password for invalid user zhengyifan from 120.70.100.89 port 34779 ssh2 ... |
2020-03-05 00:09:32 |
| 113.172.212.176 | attackspambots | suspicious action Wed, 04 Mar 2020 10:36:04 -0300 |
2020-03-05 00:10:27 |
| 222.169.185.234 | attack | 2020-03-04T14:36:08.283948vps773228.ovh.net sshd[29434]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.169.185.234 2020-03-04T14:36:08.274545vps773228.ovh.net sshd[29434]: Invalid user deploy from 222.169.185.234 port 33798 2020-03-04T14:36:09.939919vps773228.ovh.net sshd[29434]: Failed password for invalid user deploy from 222.169.185.234 port 33798 ssh2 2020-03-04T15:44:30.696333vps773228.ovh.net sshd[30253]: Invalid user sysop from 222.169.185.234 port 60594 2020-03-04T15:44:30.709476vps773228.ovh.net sshd[30253]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.169.185.234 2020-03-04T15:44:30.696333vps773228.ovh.net sshd[30253]: Invalid user sysop from 222.169.185.234 port 60594 2020-03-04T15:44:32.495898vps773228.ovh.net sshd[30253]: Failed password for invalid user sysop from 222.169.185.234 port 60594 ssh2 2020-03-04T15:56:19.786036vps773228.ovh.net sshd[30391]: Invalid user web from 222.169 ... |
2020-03-04 23:59:12 |