城市(city): unknown
省份(region): unknown
国家(country): Netherlands (the)
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 145.138.233.109
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 54799
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;145.138.233.109. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025021400 1800 900 604800 86400
;; Query time: 13 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 14 17:07:15 CST 2025
;; MSG SIZE rcvd: 108
109.233.138.145.in-addr.arpa domain name pointer 145.138.EARLY-REGISTRATION.of.SURFnet.invalid.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
109.233.138.145.in-addr.arpa name = 145.138.EARLY-REGISTRATION.of.SURFnet.invalid.
Authoritative answers can be found from:
| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 49.69.205.106 | attackspam | Aug 31 16:20:07 nxxxxxxx sshd[13756]: refused connect from 49.69.205.106 (49= .69.205.106) ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=49.69.205.106 |
2020-09-07 15:04:12 |
| 104.46.32.174 | attackbotsspam | Unauthorised login to NAS |
2020-09-07 16:02:18 |
| 185.248.160.21 | attack | malicious Brute-Force reported by https://www.patrick-binder.de ... |
2020-09-07 15:11:58 |
| 78.36.44.250 | attack | Automatic report - Port Scan Attack |
2020-09-07 15:46:50 |
| 185.158.142.144 | attack | Honeypot attack, port: 445, PTR: 144-142-158-185.wifi4all.it. |
2020-09-07 15:57:54 |
| 222.89.70.216 | attackbotsspam |
|
2020-09-07 15:20:37 |
| 23.108.46.43 | attackspam | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found drmichaeltwalsh.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-09-07 15:15:45 |
| 93.72.114.171 | attack | [Sun Sep 06 21:11:17 2020] - Syn Flood From IP: 93.72.114.171 Port: 53999 |
2020-09-07 15:58:55 |
| 45.142.120.192 | attackbotsspam | Sep 7 09:45:10 srv01 postfix/smtpd\[27802\]: warning: unknown\[45.142.120.192\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Sep 7 09:45:26 srv01 postfix/smtpd\[29439\]: warning: unknown\[45.142.120.192\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Sep 7 09:45:27 srv01 postfix/smtpd\[27802\]: warning: unknown\[45.142.120.192\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Sep 7 09:45:42 srv01 postfix/smtpd\[27156\]: warning: unknown\[45.142.120.192\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Sep 7 09:46:00 srv01 postfix/smtpd\[29440\]: warning: unknown\[45.142.120.192\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 ... |
2020-09-07 15:51:12 |
| 60.2.10.190 | attackspambots | $f2bV_matches |
2020-09-07 15:21:42 |
| 49.232.59.246 | attack | ... |
2020-09-07 15:22:39 |
| 51.68.11.199 | attackbots | CMS (WordPress or Joomla) login attempt. |
2020-09-07 15:54:38 |
| 103.75.101.59 | attack | $f2bV_matches |
2020-09-07 15:23:04 |
| 109.64.66.118 | attackbots | Unauthorised login to NAS |
2020-09-07 15:22:11 |
| 77.240.156.234 | attack | Sep 1 06:44:40 georgia postfix/smtpd[40206]: connect from unknown[77.240.156.234] Sep 1 06:44:40 georgia postfix/smtpd[40206]: lost connection after CONNECT from unknown[77.240.156.234] Sep 1 06:44:40 georgia postfix/smtpd[40206]: disconnect from unknown[77.240.156.234] commands=0/0 Sep 1 06:44:51 georgia postfix/smtpd[40204]: connect from unknown[77.240.156.234] Sep 1 06:44:51 georgia postfix/smtpd[40204]: lost connection after CONNECT from unknown[77.240.156.234] Sep 1 06:44:51 georgia postfix/smtpd[40204]: disconnect from unknown[77.240.156.234] commands=0/0 Sep 1 06:45:01 georgia postfix/smtpd[45769]: connect from unknown[77.240.156.234] Sep 1 06:45:01 georgia postfix/smtpd[45769]: lost connection after CONNECT from unknown[77.240.156.234] Sep 1 06:45:01 georgia postfix/smtpd[45769]: disconnect from unknown[77.240.156.234] commands=0/0 Sep 1 06:45:13 georgia postfix/smtpd[40204]: connect from unknown[77.240.156.234] Sep 1 06:45:13 georgia postfix/smtpd[40........ ------------------------------- |
2020-09-07 15:08:53 |