城市(city): unknown
省份(region): unknown
国家(country): United States
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 50.139.71.19
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 62730
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;50.139.71.19. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025062800 1800 900 604800 86400
;; Query time: 10 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Jun 28 15:28:52 CST 2025
;; MSG SIZE rcvd: 105
19.71.139.50.in-addr.arpa domain name pointer c-50-139-71-19.hsd1.or.comcast.net.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
19.71.139.50.in-addr.arpa name = c-50-139-71-19.hsd1.or.comcast.net.
Authoritative answers can be found from:
IP | 类型 | 评论内容 | 时间 |
---|---|---|---|
120.203.29.78 | attackspam | web-1 [ssh] SSH Attack |
2020-08-29 05:53:43 |
98.142.143.152 | attackbotsspam | Invalid user pay from 98.142.143.152 port 56176 |
2020-08-29 06:20:37 |
36.112.136.33 | attack | 2020-08-28 13:24:49,821 fail2ban.actions [937]: NOTICE [sshd] Ban 36.112.136.33 2020-08-28 14:02:10,172 fail2ban.actions [937]: NOTICE [sshd] Ban 36.112.136.33 2020-08-28 14:40:34,361 fail2ban.actions [937]: NOTICE [sshd] Ban 36.112.136.33 2020-08-28 22:30:55,521 fail2ban.actions [937]: NOTICE [sshd] Ban 36.112.136.33 2020-08-28 23:06:25,408 fail2ban.actions [937]: NOTICE [sshd] Ban 36.112.136.33 ... |
2020-08-29 06:13:14 |
188.131.138.175 | attack | Aug 28 23:10:56 master sshd[2230]: Failed password for invalid user aek from 188.131.138.175 port 47730 ssh2 Aug 28 23:33:10 master sshd[2839]: Failed password for root from 188.131.138.175 port 54282 ssh2 Aug 28 23:38:55 master sshd[2887]: Failed password for invalid user vvk from 188.131.138.175 port 58576 ssh2 Aug 28 23:44:32 master sshd[3013]: Failed password for invalid user ftpuser from 188.131.138.175 port 34636 ssh2 Aug 28 23:50:14 master sshd[3147]: Failed password for invalid user moon from 188.131.138.175 port 38928 ssh2 Aug 29 00:01:33 master sshd[3660]: Failed password for invalid user wf from 188.131.138.175 port 47506 ssh2 Aug 29 00:07:08 master sshd[3714]: Failed password for invalid user esteban from 188.131.138.175 port 51794 ssh2 Aug 29 00:12:43 master sshd[3836]: Failed password for invalid user alexis from 188.131.138.175 port 56074 ssh2 Aug 29 00:23:48 master sshd[3999]: Failed password for root from 188.131.138.175 port 36408 ssh2 |
2020-08-29 06:13:29 |
67.49.253.28 | attack | 2020-08-2822:23:251kBkuC-00013d-KY\<=simone@gedacom.chH=\(localhost\)[122.155.39.250]:50003P=esmtpsaX=TLS1.2:ECDHE-RSA-AES256-GCM-SHA384:256CV=noA=dovecot_login:simone@gedacom.chS=1890id=DDD86E3D36E2CC7FA3A6EF57936D6451@gedacom.chT="Thereiscertainlynotonepersonjustlikemyselfonthisplanet"forhanad338@gmail.com2020-08-2822:23:021kBktq-00012R-FC\<=simone@gedacom.chH=\(localhost\)[14.186.15.141]:45356P=esmtpsaX=TLS1.2:ECDHE-RSA-AES256-GCM-SHA384:256CV=noA=dovecot_login:simone@gedacom.chS=1896id=C7C274272CF8D665B9BCF54D891F458D@gedacom.chT="Iamactuallyseekingoutapersonwithawonderfulsoul"formartinmunozmota863@gmail.com2020-08-2822:22:431kBktX-00011W-Px\<=simone@gedacom.chH=host-79-7-86-18.business.telecomitalia.it\(localhost\)[79.7.86.18]:50862P=esmtpsaX=TLS1.2:ECDHE-RSA-AES256-GCM-SHA384:256CV=noA=dovecot_login:simone@gedacom.chS=1827id=1217A1F2F92D03B06C6920985C0CAFB9@gedacom.chT="Imayofferexactlywhatthemajorityoffemalescannot"forperaltaaaron99@yahoo.com2020-08-2822:23:111kBkty-000130-Gz\<=simone@gedacom.chH |
2020-08-29 06:12:52 |
154.16.203.118 | attackbots | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found drjamieswellnesscenter.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 softw |
2020-08-29 06:08:24 |
222.186.30.59 | attack | Aug 29 00:00:46 vps639187 sshd\[19950\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.30.59 user=root Aug 29 00:00:49 vps639187 sshd\[19950\]: Failed password for root from 222.186.30.59 port 49287 ssh2 Aug 29 00:00:51 vps639187 sshd\[19950\]: Failed password for root from 222.186.30.59 port 49287 ssh2 ... |
2020-08-29 06:06:09 |
47.188.43.153 | attack | Aug 28 22:05:28 gamehost-one sshd[27172]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=47.188.43.153 Aug 28 22:05:29 gamehost-one sshd[27172]: Failed password for invalid user loop from 47.188.43.153 port 39576 ssh2 Aug 28 22:23:50 gamehost-one sshd[28653]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=47.188.43.153 ... |
2020-08-29 06:00:14 |
193.56.240.140 | attack | fail2ban/Aug 28 22:19:49 h1962932 sshd[29148]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.56.240.140 user=root Aug 28 22:19:51 h1962932 sshd[29148]: Failed password for root from 193.56.240.140 port 42650 ssh2 Aug 28 22:23:28 h1962932 sshd[29220]: Invalid user blair from 193.56.240.140 port 50484 Aug 28 22:23:28 h1962932 sshd[29220]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.56.240.140 Aug 28 22:23:28 h1962932 sshd[29220]: Invalid user blair from 193.56.240.140 port 50484 Aug 28 22:23:30 h1962932 sshd[29220]: Failed password for invalid user blair from 193.56.240.140 port 50484 ssh2 |
2020-08-29 06:16:46 |
198.46.189.106 | attack | SSH Brute-Force. Ports scanning. |
2020-08-29 05:51:36 |
106.12.57.149 | attack | Invalid user oracle from 106.12.57.149 port 60870 |
2020-08-29 06:18:00 |
206.189.129.144 | attackbots | Invalid user tyb from 206.189.129.144 port 55786 |
2020-08-29 06:19:49 |
209.141.61.233 | attackspam | Fail2Ban Ban Triggered |
2020-08-29 06:10:33 |
211.253.27.146 | attackbots | Invalid user denis from 211.253.27.146 port 35800 |
2020-08-29 05:59:48 |
124.197.159.114 | attackspambots | 28.08.2020 22:24:01 - RDP Login Fail Detected by https://www.elinox.de/RDP-Wächter |
2020-08-29 05:53:14 |