城市(city): Singapore
省份(region): unknown
国家(country): Singapore
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2025, American Registry for Internet Numbers, Ltd.
#
NetRange: 169.150.192.0 - 169.150.255.255
CIDR: 169.150.192.0/18
NetName: RIPE
NetHandle: NET-169-150-192-0-1
Parent: NET169 (NET-169-0-0-0-0)
NetType: Early Registrations, Transferred to RIPE NCC
OriginAS:
Organization: RIPE Network Coordination Centre (RIPE)
RegDate: 2022-03-14
Updated: 2025-02-10
Comment: These addresses have been further assigned to users in the RIPE NCC region. Please note that the organization and point of contact details listed below are those of the RIPE NCC not the current address holder. ** You can find user contact information for the current address holder in the RIPE database at http://www.ripe.net/whois.
Ref: https://rdap.arin.net/registry/ip/169.150.192.0
ResourceLink: https://apps.db.ripe.net/db-web-ui/query
ResourceLink: whois.ripe.net
OrgName: RIPE Network Coordination Centre
OrgId: RIPE
Address: P.O. Box 10096
City: Amsterdam
StateProv:
PostalCode: 1001EB
Country: NL
RegDate:
Updated: 2013-07-29
Ref: https://rdap.arin.net/registry/entity/RIPE
ReferralServer: whois.ripe.net
ResourceLink: https://apps.db.ripe.net/db-web-ui/query
OrgTechHandle: RNO29-ARIN
OrgTechName: RIPE NCC Operations
OrgTechPhone: +31 20 535 4444
OrgTechEmail: hostmaster@ripe.net
OrgTechRef: https://rdap.arin.net/registry/entity/RNO29-ARIN
OrgAbuseHandle: ABUSE3850-ARIN
OrgAbuseName: Abuse Contact
OrgAbusePhone: +31205354444
OrgAbuseEmail: abuse@ripe.net
OrgAbuseRef: https://rdap.arin.net/registry/entity/ABUSE3850-ARIN
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2025, American Registry for Internet Numbers, Ltd.
#; <<>> DiG 9.10.3-P4-Ubuntu <<>> 169.150.207.234
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 6639
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;169.150.207.234. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025120800 1800 900 604800 86400
;; Query time: 11 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Dec 08 20:41:30 CST 2025
;; MSG SIZE rcvd: 108b'234.207.150.169.in-addr.arpa domain name pointer unn-169-150-207-234.datapacket.com.
'Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
234.207.150.169.in-addr.arpa name = unn-169-150-207-234.datapacket.com.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 49.88.112.70 | attackspam | Oct 22 14:15:51 MK-Soft-VM3 sshd[24718]: Failed password for root from 49.88.112.70 port 38404 ssh2 Oct 22 14:15:54 MK-Soft-VM3 sshd[24718]: Failed password for root from 49.88.112.70 port 38404 ssh2 ... |
2019-10-22 21:06:47 |
| 165.227.22.111 | attackspam | chaangnoifulda.de 165.227.22.111 \[22/Oct/2019:13:52:59 +0200\] "POST /wp-login.php HTTP/1.1" 200 5874 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0" chaangnoifulda.de 165.227.22.111 \[22/Oct/2019:13:53:01 +0200\] "POST /wp-login.php HTTP/1.1" 200 5833 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0" |
2019-10-22 20:38:12 |
| 187.0.160.130 | attackspam | Feb 5 09:55:16 microserver sshd[35547]: Invalid user ftp_user from 187.0.160.130 port 39200 Feb 5 09:55:16 microserver sshd[35547]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.0.160.130 Feb 5 09:55:18 microserver sshd[35547]: Failed password for invalid user ftp_user from 187.0.160.130 port 39200 ssh2 Feb 5 09:59:56 microserver sshd[35632]: Invalid user system from 187.0.160.130 port 35994 Feb 5 09:59:56 microserver sshd[35632]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.0.160.130 Feb 19 08:07:48 microserver sshd[20348]: Invalid user bridge from 187.0.160.130 port 48264 Feb 19 08:07:48 microserver sshd[20348]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.0.160.130 Feb 19 08:07:50 microserver sshd[20348]: Failed password for invalid user bridge from 187.0.160.130 port 48264 ssh2 Feb 19 08:15:10 microserver sshd[21120]: Invalid user catego from 187.0.160.130 port 4 |
2019-10-22 20:59:07 |
| 222.136.250.85 | attackbots | IP Ban Report : https://help-dysk.pl/wordpress-firewall-plugins/ip/222.136.250.85/ CN - 1H : (416) Protection Against DDoS WordPress plugin : "odzyskiwanie danych help-dysk" IP Address Ranges by Country : CN NAME ASN : ASN4837 IP : 222.136.250.85 CIDR : 222.136.0.0/13 PREFIX COUNT : 1262 UNIQUE IP COUNT : 56665856 ATTACKS DETECTED ASN4837 : 1H - 7 3H - 19 6H - 42 12H - 78 24H - 141 DateTime : 2019-10-22 13:52:11 INFO : Port Scan TELNET Detected and Blocked by ADMIN - data recovery |
2019-10-22 21:11:34 |
| 202.175.46.170 | attack | Invalid user nagios from 202.175.46.170 port 51490 |
2019-10-22 20:51:03 |
| 219.83.162.23 | attackbots | SSH scan :: |
2019-10-22 21:04:07 |
| 178.128.158.113 | attackspambots | Invalid user usuario from 178.128.158.113 port 54736 |
2019-10-22 20:24:41 |
| 68.45.62.109 | attackbotsspam | 2019-10-22T12:57:13.416210abusebot-4.cloudsearch.cf sshd\[26105\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=c-68-45-62-109.hsd1.nj.comcast.net user=root |
2019-10-22 21:03:44 |
| 139.162.184.156 | attackspam | SSH-bruteforce attempts |
2019-10-22 20:47:46 |
| 103.141.138.125 | attackbots | 2019-10-22T18:52:50.061731enmeeting.mahidol.ac.th sshd\[18359\]: User root from 103.141.138.125 not allowed because not listed in AllowUsers 2019-10-22T18:52:50.187470enmeeting.mahidol.ac.th sshd\[18359\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.141.138.125 user=root 2019-10-22T18:52:52.461042enmeeting.mahidol.ac.th sshd\[18359\]: Failed password for invalid user root from 103.141.138.125 port 58567 ssh2 ... |
2019-10-22 20:43:34 |
| 93.34.85.54 | attack | ENG,WP GET /wp-login.php |
2019-10-22 20:55:29 |
| 185.92.247.200 | attackbotsspam | WordPress wp-login brute force :: 185.92.247.200 0.040 BYPASS [22/Oct/2019:22:52:29 1100] [censored_2] "POST /wp-login.php HTTP/1.1" 200 4630 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" |
2019-10-22 21:05:38 |
| 196.9.24.40 | attack | Oct 22 15:08:43 www sshd\[13136\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=196.9.24.40 user=root Oct 22 15:08:45 www sshd\[13136\]: Failed password for root from 196.9.24.40 port 57148 ssh2 Oct 22 15:13:53 www sshd\[13225\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=196.9.24.40 user=root ... |
2019-10-22 20:32:33 |
| 144.217.242.111 | attackspambots | 2019-10-22T12:11:44.023992shield sshd\[27586\]: Invalid user ubuntu from 144.217.242.111 port 43018 2019-10-22T12:11:44.028378shield sshd\[27586\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.ip-144-217-242.net 2019-10-22T12:11:45.992459shield sshd\[27586\]: Failed password for invalid user ubuntu from 144.217.242.111 port 43018 ssh2 2019-10-22T12:15:38.205676shield sshd\[28429\]: Invalid user temp from 144.217.242.111 port 53870 2019-10-22T12:15:38.210069shield sshd\[28429\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.ip-144-217-242.net |
2019-10-22 20:23:04 |
| 79.131.204.87 | attackbots | Unauthorized IMAP connection attempt |
2019-10-22 20:22:05 |