City: Taichung
Region: Taichung City
Country: Taiwan, China
Internet Service Provider: unknown
Hostname: unknown
Organization: Data Communication Business Group
Usage Type: unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 114.41.141.4
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 55453
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;114.41.141.4. IN A
;; AUTHORITY SECTION:
. 1683 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2019052500 1800 900 604800 86400
;; Query time: 1 msec
;; SERVER: 67.207.67.2#53(67.207.67.2)
;; WHEN: Sat May 25 23:50:22 CST 2019
;; MSG SIZE rcvd: 116
4.141.41.114.in-addr.arpa domain name pointer 114-41-141-4.dynamic-ip.hinet.net.
Server: 67.207.67.2
Address: 67.207.67.2#53
Non-authoritative answer:
4.141.41.114.in-addr.arpa name = 114-41-141-4.dynamic-ip.hinet.net.
Authoritative answers can be found from:
IP | Type | Details | Datetime |
---|---|---|---|
117.184.114.139 | attackbotsspam | Unauthorized connection attempt detected from IP address 117.184.114.139 to port 2220 [J] |
2020-02-02 20:12:33 |
107.6.171.134 | attackbots | Port 22 Scan, PTR: sh-ams-nl-gp1-wk104.internet-census.org. |
2020-02-02 20:09:19 |
41.33.179.90 | attackbotsspam | Unauthorized connection attempt detected from IP address 41.33.179.90 to port 1433 [J] |
2020-02-02 19:46:52 |
91.232.96.29 | attack | Feb 2 05:50:09 grey postfix/smtpd\[392\]: NOQUEUE: reject: RCPT from expect.msaysha.com\[91.232.96.29\]: 554 5.7.1 Service unavailable\; Client host \[91.232.96.29\] blocked using truncate.gbudb.net\; http://www.gbudb.com/truncate/ \[91.232.96.29\]\; from=\ |
2020-02-02 20:07:50 |
23.254.46.120 | attackspambots | (From victoriashort44@gmail.com) Hi there! Have you considered making some upgrades on your website? Allow me to assist you. I'm a freelance web designer/developer that's dedicated to helping businesses grow, and I do this by making sure that your website is the best that it can be in terms of aesthetics, functionality and reliability in handling your business online. Are there any particular features that you've thought of adding? How about giving your site a more modern user-interface that's more suitable for your business? I'd like to talk to you about it on a time that's best for you. I can give you plenty of information and examples of what I've done for other clients and what the results have been. Kindly let me know if you're interested, and I'll get in touch with you at a time you prefer. I'm hoping we can talk soon! Thanks! Victoria Short - Web Development and Business Optimization Specialist |
2020-02-02 20:20:29 |
143.95.34.83 | attackbots | Port 22 Scan, PTR: None |
2020-02-02 20:07:16 |
176.36.192.193 | attackbots | Unauthorized connection attempt detected from IP address 176.36.192.193 to port 2220 [J] |
2020-02-02 19:49:25 |
42.119.199.185 | attackspambots | Unauthorized connection attempt detected from IP address 42.119.199.185 to port 23 [J] |
2020-02-02 19:42:31 |
125.124.19.97 | attackbotsspam | Unauthorized connection attempt detected from IP address 125.124.19.97 to port 2220 [J] |
2020-02-02 19:51:10 |
185.211.245.198 | attack | Feb 2 12:51:19 s1 postfix/submission/smtpd\[14825\]: warning: unknown\[185.211.245.198\]: SASL PLAIN authentication failed: Feb 2 12:51:19 s1 postfix/submission/smtpd\[14826\]: warning: unknown\[185.211.245.198\]: SASL PLAIN authentication failed: Feb 2 12:51:19 s1 postfix/submission/smtpd\[14829\]: warning: unknown\[185.211.245.198\]: SASL PLAIN authentication failed: Feb 2 12:51:19 s1 postfix/submission/smtpd\[14827\]: warning: unknown\[185.211.245.198\]: SASL PLAIN authentication failed: Feb 2 12:51:19 s1 postfix/submission/smtpd\[14828\]: warning: unknown\[185.211.245.198\]: SASL PLAIN authentication failed: Feb 2 12:51:26 s1 postfix/submission/smtpd\[14826\]: warning: unknown\[185.211.245.198\]: SASL PLAIN authentication failed: Feb 2 12:51:26 s1 postfix/submission/smtpd\[14829\]: warning: unknown\[185.211.245.198\]: SASL PLAIN authentication failed: Feb 2 12:51:26 s1 postfix/submission/smtpd\[14828\]: warning: unknown\[185.211.245.198\]: SASL PLAIN authentication failed: Feb 2 12:51:26 s1 postf |
2020-02-02 19:57:17 |
41.86.10.20 | attackbots | Unauthorized connection attempt detected from IP address 41.86.10.20 to port 2220 [J] |
2020-02-02 19:42:46 |
173.242.131.72 | attackspam | "SERVER-WEBAPP GPON Router authentication bypass and command injection attempt" |
2020-02-02 20:13:49 |
111.229.4.117 | attackbotsspam | Feb 2 12:36:00 MK-Soft-Root2 sshd[15150]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.229.4.117 Feb 2 12:36:02 MK-Soft-Root2 sshd[15150]: Failed password for invalid user user5 from 111.229.4.117 port 40418 ssh2 ... |
2020-02-02 20:19:18 |
152.0.121.227 | attackbotsspam | Hits on port : 8080 |
2020-02-02 19:41:59 |
36.73.99.168 | attackbotsspam | Attempt to attack host OS, exploiting network vulnerabilities, on 02-02-2020 04:50:09. |
2020-02-02 20:08:47 |