城市(city): unknown
省份(region): unknown
国家(country): Russian Federation (the)
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 5.18.50.83
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 38439
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;5.18.50.83. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025012701 1800 900 604800 86400
;; Query time: 12 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Jan 28 03:02:51 CST 2025
;; MSG SIZE rcvd: 10383.50.18.5.in-addr.arpa domain name pointer 5x18x50x83.static-business.spb.ertelecom.ru.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
83.50.18.5.in-addr.arpa name = 5x18x50x83.static-business.spb.ertelecom.ru.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 178.128.112.147 | attackbots | Unauthorized connection attempt detected from IP address 178.128.112.147 to port 2220 [J] |
2020-01-20 22:42:09 |
| 165.227.115.93 | attack | Unauthorized connection attempt detected from IP address 165.227.115.93 to port 2220 [J] |
2020-01-20 22:56:41 |
| 1.20.179.87 | attack | Unauthorized connection attempt detected from IP address 1.20.179.87 to port 445 [T] |
2020-01-20 23:12:10 |
| 174.255.132.202 | attack | I suspect this IP address is being used by my ex and associates.,aka fellow convicts, it is with Verizon which seems to be the carrier always used. it was inconclusive on location, is that something you can assist with? Sincerely Jeanie Smith 8175834552 |
2020-01-20 22:49:13 |
| 175.172.161.54 | attackbotsspam | Unauthorized connection attempt detected from IP address 175.172.161.54 to port 8080 [T] |
2020-01-20 23:17:59 |
| 66.249.75.219 | attackspam | WEB_SERVER 403 Forbidden |
2020-01-20 22:47:26 |
| 123.134.94.70 | attackspambots | Unauthorized connection attempt detected from IP address 123.134.94.70 to port 23 [T] |
2020-01-20 22:58:55 |
| 80.66.81.143 | attackbots | Jan 20 15:26:58 relay postfix/smtpd\[16556\]: warning: unknown\[80.66.81.143\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jan 20 15:27:17 relay postfix/smtpd\[15476\]: warning: unknown\[80.66.81.143\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jan 20 15:29:11 relay postfix/smtpd\[15915\]: warning: unknown\[80.66.81.143\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jan 20 15:29:31 relay postfix/smtpd\[15915\]: warning: unknown\[80.66.81.143\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jan 20 15:30:12 relay postfix/smtpd\[22982\]: warning: unknown\[80.66.81.143\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 ... |
2020-01-20 22:43:06 |
| 42.117.20.137 | attackspam | Unauthorized connection attempt detected from IP address 42.117.20.137 to port 23 [J] |
2020-01-20 23:09:28 |
| 101.68.202.22 | attackbotsspam | Unauthorized connection attempt detected from IP address 101.68.202.22 to port 23 [J] |
2020-01-20 23:04:30 |
| 120.203.5.92 | attackbots | Unauthorized connection attempt detected from IP address 120.203.5.92 to port 23 [T] |
2020-01-20 23:00:06 |
| 180.158.212.107 | attackbotsspam | Unauthorized connection attempt detected from IP address 180.158.212.107 to port 445 [T] |
2020-01-20 22:55:55 |
| 45.141.84.44 | attackspam | Unauthorized connection attempt detected from IP address 45.141.84.44 to port 51 [T] |
2020-01-20 23:08:09 |
| 125.25.160.146 | attackspam | Unauthorized connection attempt detected from IP address 125.25.160.146 to port 80 [T] |
2020-01-20 23:23:04 |
| 139.219.6.50 | attackbots | Portscan or hack attempt detected by psad/fwsnort |
2020-01-20 23:22:05 |