城市(city): Des Moines
省份(region): Iowa
国家(country): United States
运营商(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-2026, American Registry for Internet Numbers, Ltd.
#
NetRange: 130.131.0.0 - 130.131.255.255
CIDR: 130.131.0.0/16
NetName: RIPE
NetHandle: NET-130-131-0-0-1
Parent: NET130 (NET-130-0-0-0-0)
NetType: Early Registrations, Transferred to RIPE NCC
OriginAS:
Organization: RIPE Network Coordination Centre (RIPE)
RegDate: 2023-09-07
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/130.131.0.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-2026, American Registry for Internet Numbers, Ltd.
#; <<>> DiG 9.10.3-P4-Ubuntu <<>> 130.131.161.148
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 30121
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;130.131.161.148. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026050502 1800 900 604800 86400
;; Query time: 5 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed May 06 06:30:23 CST 2026
;; MSG SIZE rcvd: 108148.161.131.130.in-addr.arpa domain name pointer azpdcgnss3xk.stretchoid.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
148.161.131.130.in-addr.arpa name = azpdcgnss3xk.stretchoid.com.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 159.203.201.242 | attackspam | 2086/tcp 9529/tcp 1527/tcp... [2019-09-12/10-24]33pkt,30pt.(tcp) |
2019-10-24 12:09:06 |
| 94.23.32.126 | attackbots | Wordpress bruteforce |
2019-10-24 12:10:50 |
| 223.82.26.9 | attackbotsspam | Automatic report - FTP Brute Force |
2019-10-24 08:07:22 |
| 81.30.212.14 | attack | Invalid user testing from 81.30.212.14 port 34284 |
2019-10-24 08:16:10 |
| 106.12.192.240 | attackspam | Oct 24 05:50:38 tux-35-217 sshd\[3562\]: Invalid user zd from 106.12.192.240 port 46750 Oct 24 05:50:38 tux-35-217 sshd\[3562\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.192.240 Oct 24 05:50:40 tux-35-217 sshd\[3562\]: Failed password for invalid user zd from 106.12.192.240 port 46750 ssh2 Oct 24 05:55:42 tux-35-217 sshd\[3596\]: Invalid user tm from 106.12.192.240 port 53030 Oct 24 05:55:42 tux-35-217 sshd\[3596\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.192.240 ... |
2019-10-24 12:17:33 |
| 119.29.242.84 | attack | Oct 24 06:15:57 localhost sshd\[1469\]: Invalid user ntadmin123 from 119.29.242.84 port 45218 Oct 24 06:15:57 localhost sshd\[1469\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.29.242.84 Oct 24 06:15:59 localhost sshd\[1469\]: Failed password for invalid user ntadmin123 from 119.29.242.84 port 45218 ssh2 |
2019-10-24 12:18:56 |
| 107.173.145.168 | attack | Oct 24 06:46:37 server sshd\[14444\]: Invalid user an from 107.173.145.168 Oct 24 06:46:37 server sshd\[14444\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=107.173.145.168 Oct 24 06:46:39 server sshd\[14444\]: Failed password for invalid user an from 107.173.145.168 port 33316 ssh2 Oct 24 06:55:48 server sshd\[16815\]: Invalid user test from 107.173.145.168 Oct 24 06:55:48 server sshd\[16815\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=107.173.145.168 ... |
2019-10-24 12:15:10 |
| 167.71.229.184 | attackbotsspam | Invalid user Admin from 167.71.229.184 port 39084 |
2019-10-24 08:24:41 |
| 45.80.64.246 | attackbotsspam | Oct 23 23:12:54 sshgateway sshd\[7382\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.80.64.246 user=root Oct 23 23:12:56 sshgateway sshd\[7382\]: Failed password for root from 45.80.64.246 port 33276 ssh2 Oct 23 23:17:40 sshgateway sshd\[7393\]: Invalid user vreugdenhil from 45.80.64.246 |
2019-10-24 08:21:39 |
| 167.114.185.237 | attack | 2019-10-23T17:15:19.896237ns525875 sshd\[20204\]: Invalid user jt from 167.114.185.237 port 52942 2019-10-23T17:15:19.898294ns525875 sshd\[20204\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=237.ip-167-114-185.net 2019-10-23T17:15:21.871468ns525875 sshd\[20204\]: Failed password for invalid user jt from 167.114.185.237 port 52942 ssh2 2019-10-23T17:18:58.129844ns525875 sshd\[22766\]: Invalid user laurelei from 167.114.185.237 port 35888 ... |
2019-10-24 08:08:08 |
| 194.37.92.48 | attackbotsspam | Oct 24 05:57:03 mail sshd[5669]: Failed password for root from 194.37.92.48 port 33523 ssh2 Oct 24 06:01:02 mail sshd[7802]: Failed password for root from 194.37.92.48 port 52874 ssh2 |
2019-10-24 12:20:12 |
| 49.247.208.209 | attackbotsspam | SSH invalid-user multiple login try |
2019-10-24 08:13:22 |
| 112.199.95.227 | attackspambots | Unauthorised access (Oct 23) SRC=112.199.95.227 LEN=40 TOS=0x08 TTL=242 ID=46236 TCP DPT=445 WINDOW=1024 SYN |
2019-10-24 08:13:01 |
| 110.18.243.70 | attack | 2019-10-24T10:55:59.524727enmeeting.mahidol.ac.th sshd\[8138\]: User root from 110.18.243.70 not allowed because not listed in AllowUsers 2019-10-24T10:55:59.651670enmeeting.mahidol.ac.th sshd\[8138\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=110.18.243.70 user=root 2019-10-24T10:56:01.897498enmeeting.mahidol.ac.th sshd\[8138\]: Failed password for invalid user root from 110.18.243.70 port 42310 ssh2 ... |
2019-10-24 12:03:24 |
| 106.13.5.233 | attack | 2019-10-24T06:50:14.985516tmaserv sshd\[26767\]: Invalid user 12345 from 106.13.5.233 port 43570 2019-10-24T06:50:14.990961tmaserv sshd\[26767\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.5.233 2019-10-24T06:50:17.205832tmaserv sshd\[26767\]: Failed password for invalid user 12345 from 106.13.5.233 port 43570 ssh2 2019-10-24T06:55:05.713424tmaserv sshd\[26986\]: Invalid user zliang from 106.13.5.233 port 53024 2019-10-24T06:55:05.719370tmaserv sshd\[26986\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.5.233 2019-10-24T06:55:07.884292tmaserv sshd\[26986\]: Failed password for invalid user zliang from 106.13.5.233 port 53024 ssh2 ... |
2019-10-24 12:06:52 |