City: Loyang
Region: unknown
Country: Singapore
Internet Service Provider: 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: 129.221.0.0 - 129.221.255.255
CIDR: 129.221.0.0/16
NetName: ORACLE-4
NetHandle: NET-129-221-0-0-1
Parent: NET129 (NET-129-0-0-0-0)
NetType: Direct Allocation
OriginAS:
Organization: Oracle Corporation (ORACLE-4)
RegDate: 2022-12-19
Updated: 2022-12-19
Ref: https://rdap.arin.net/registry/ip/129.221.0.0
OrgName: Oracle Corporation
OrgId: ORACLE-4
Address: 2300 Oracle Way
Address: Attn: Domain Administrator
City: Austin
StateProv: TX
PostalCode: 78741
Country: US
RegDate: 1988-04-29
Updated: 2024-11-07
Ref: https://rdap.arin.net/registry/entity/ORACLE-4
OrgRoutingHandle: ORACL2-ARIN
OrgRoutingName: ORACLEROUTING
OrgRoutingPhone: +1-800-392-2999
OrgRoutingEmail: network-contact_ww@oracle.com
OrgRoutingRef: https://rdap.arin.net/registry/entity/ORACL2-ARIN
OrgAbuseHandle: NISAM-ARIN
OrgAbuseName: Network Information Systems Abuse Management
OrgAbusePhone: +1-800-633-0738
OrgAbuseEmail: abuse@oracleemaildelivery.com
OrgAbuseRef: https://rdap.arin.net/registry/entity/NISAM-ARIN
OrgTechHandle: ORACL1-ARIN
OrgTechName: ORACLE NIS
OrgTechPhone: +1-800-633-0738
OrgTechEmail: domain-contact_ww_grp@oracle.com
OrgTechRef: https://rdap.arin.net/registry/entity/ORACL1-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 <<>> 129.221.133.200
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 28653
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;129.221.133.200. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026111000 1800 900 604800 86400
;; Query time: 7 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Nov 10 15:00:42 CST 2026
;; MSG SIZE rcvd: 108Host 200.133.221.129.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 200.133.221.129.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 104.236.156.136 | attack | (sshd) Failed SSH login from 104.236.156.136 (US/United States/supost.com): 5 in the last 3600 secs |
2020-04-20 02:25:28 |
| 152.136.101.65 | attack | Apr 20 00:16:58 webhost01 sshd[29316]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=152.136.101.65 Apr 20 00:17:00 webhost01 sshd[29316]: Failed password for invalid user vb from 152.136.101.65 port 51102 ssh2 ... |
2020-04-20 02:09:53 |
| 67.198.232.59 | attack | firewall-block, port(s): 1433/tcp |
2020-04-20 02:13:42 |
| 103.91.53.30 | attack | Tried sshing with brute force. |
2020-04-20 01:53:43 |
| 116.109.99.64 | attack | Unauthorized connection attempt from IP address 116.109.99.64 on Port 445(SMB) |
2020-04-20 02:18:05 |
| 181.48.55.42 | attackspambots | Apr 19 12:00:00 XXX sshd[1863]: Invalid user sybase from 181.48.55.42 port 61534 |
2020-04-20 02:23:36 |
| 50.235.176.173 | attack | Unauthorized connection attempt from IP address 50.235.176.173 on Port 445(SMB) |
2020-04-20 01:49:48 |
| 95.58.18.178 | attack | Unauthorized connection attempt from IP address 95.58.18.178 on Port 445(SMB) |
2020-04-20 01:57:26 |
| 115.159.66.109 | attackspam | SSH Brute Force |
2020-04-20 02:13:07 |
| 109.87.151.216 | attackbotsspam | 1587297619 - 04/19/2020 14:00:19 Host: 109.87.151.216/109.87.151.216 Port: 445 TCP Blocked |
2020-04-20 01:50:20 |
| 197.156.104.14 | attack | Unauthorized connection attempt from IP address 197.156.104.14 on Port 445(SMB) |
2020-04-20 01:52:07 |
| 151.80.235.228 | attackbots | 2020-04-19T18:30:21.442389vps773228.ovh.net sshd[9566]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=228.ip-151-80-235.eu 2020-04-19T18:30:21.428752vps773228.ovh.net sshd[9566]: Invalid user mr from 151.80.235.228 port 47762 2020-04-19T18:30:23.352876vps773228.ovh.net sshd[9566]: Failed password for invalid user mr from 151.80.235.228 port 47762 ssh2 2020-04-19T18:37:17.784514vps773228.ovh.net sshd[9698]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=228.ip-151-80-235.eu user=root 2020-04-19T18:37:20.472775vps773228.ovh.net sshd[9698]: Failed password for root from 151.80.235.228 port 39248 ssh2 ... |
2020-04-20 02:06:01 |
| 106.75.7.92 | attack | Apr 19 19:28:23 vpn01 sshd[2630]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.75.7.92 Apr 19 19:28:25 vpn01 sshd[2630]: Failed password for invalid user test from 106.75.7.92 port 48370 ssh2 ... |
2020-04-20 02:18:45 |
| 222.186.180.130 | attackspam | 04/19/2020-13:40:53.156933 222.186.180.130 Protocol: 6 ET SCAN Potential SSH Scan |
2020-04-20 01:47:00 |
| 188.166.251.156 | attack | Apr 14 20:44:02 lock-38 sshd[1003895]: Failed password for invalid user noc from 188.166.251.156 port 48750 ssh2 Apr 14 20:47:40 lock-38 sshd[1004001]: Invalid user j from 188.166.251.156 port 43898 Apr 14 20:47:40 lock-38 sshd[1004001]: Invalid user j from 188.166.251.156 port 43898 Apr 14 20:47:40 lock-38 sshd[1004001]: Failed password for invalid user j from 188.166.251.156 port 43898 ssh2 Apr 14 20:49:50 lock-38 sshd[1004054]: Failed password for root from 188.166.251.156 port 51096 ssh2 ... |
2020-04-20 02:21:15 |