City: Sanaa
Region: Amanat Al Asimah
Country: Yemen
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: 134.35.0.0 - 134.35.255.255
CIDR: 134.35.0.0/16
NetName: RIPE
NetHandle: NET-134-35-0-0-1
Parent: NET134 (NET-134-0-0-0-0)
NetType: Early Registrations, Transferred to RIPE NCC
OriginAS:
Organization: RIPE Network Coordination Centre (RIPE)
RegDate: 2016-03-09
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/134.35.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 <<>> 134.35.157.40
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 24816
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;134.35.157.40. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026030301 1800 900 604800 86400
;; Query time: 28 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 04 11:02:12 CST 2026
;; MSG SIZE rcvd: 106
Host 40.157.35.134.in-addr.arpa. not found: 3(NXDOMAIN)
Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 40.157.35.134.in-addr.arpa: NXDOMAIN
| IP | Type | Details | Datetime |
|---|---|---|---|
| 218.94.136.90 | attackbotsspam | Dec 2 06:38:59 * sshd[11298]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.94.136.90 Dec 2 06:39:01 * sshd[11298]: Failed password for invalid user sistema from 218.94.136.90 port 56796 ssh2 |
2019-12-02 13:51:56 |
| 24.42.207.235 | attackbotsspam | Dec 2 01:05:13 TORMINT sshd\[3171\]: Invalid user nfs from 24.42.207.235 Dec 2 01:05:13 TORMINT sshd\[3171\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=24.42.207.235 Dec 2 01:05:15 TORMINT sshd\[3171\]: Failed password for invalid user nfs from 24.42.207.235 port 58872 ssh2 ... |
2019-12-02 14:21:28 |
| 163.172.84.50 | attackbotsspam | Dec 2 00:51:06 linuxvps sshd\[52372\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=163.172.84.50 user=uucp Dec 2 00:51:09 linuxvps sshd\[52372\]: Failed password for uucp from 163.172.84.50 port 58028 ssh2 Dec 2 00:57:01 linuxvps sshd\[56093\]: Invalid user test from 163.172.84.50 Dec 2 00:57:01 linuxvps sshd\[56093\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=163.172.84.50 Dec 2 00:57:03 linuxvps sshd\[56093\]: Failed password for invalid user test from 163.172.84.50 port 35644 ssh2 |
2019-12-02 14:01:31 |
| 152.32.134.90 | attack | Dec 1 19:51:48 web1 sshd\[15546\]: Invalid user suddarth from 152.32.134.90 Dec 1 19:51:48 web1 sshd\[15546\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=152.32.134.90 Dec 1 19:51:50 web1 sshd\[15546\]: Failed password for invalid user suddarth from 152.32.134.90 port 55288 ssh2 Dec 1 19:57:54 web1 sshd\[16137\]: Invalid user salter from 152.32.134.90 Dec 1 19:57:54 web1 sshd\[16137\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=152.32.134.90 |
2019-12-02 14:06:22 |
| 188.166.105.228 | attack | Dec 2 01:05:16 ny01 sshd[11544]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.166.105.228 Dec 2 01:05:17 ny01 sshd[11544]: Failed password for invalid user ssh from 188.166.105.228 port 33168 ssh2 Dec 2 01:10:50 ny01 sshd[12128]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.166.105.228 |
2019-12-02 14:14:07 |
| 94.102.49.193 | attackbots | abuseConfidenceScore blocked for 12h |
2019-12-02 13:53:03 |
| 71.6.146.185 | attackbots | 12/02/2019-00:38:50.775292 71.6.146.185 Protocol: 6 ET CINS Active Threat Intelligence Poor Reputation IP group 71 |
2019-12-02 14:03:45 |
| 112.85.42.177 | attackspam | 2019-12-02T06:37:38.579186struts4.enskede.local sshd\[15665\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.177 user=root 2019-12-02T06:37:41.468905struts4.enskede.local sshd\[15665\]: Failed password for root from 112.85.42.177 port 1266 ssh2 2019-12-02T06:37:46.823055struts4.enskede.local sshd\[15665\]: Failed password for root from 112.85.42.177 port 1266 ssh2 2019-12-02T06:37:51.080955struts4.enskede.local sshd\[15665\]: Failed password for root from 112.85.42.177 port 1266 ssh2 2019-12-02T06:37:55.158655struts4.enskede.local sshd\[15665\]: Failed password for root from 112.85.42.177 port 1266 ssh2 ... |
2019-12-02 13:40:48 |
| 216.218.206.107 | attackspam | firewall-block, port(s): 111/udp |
2019-12-02 13:50:54 |
| 106.13.103.132 | attackbotsspam | Dec 2 06:53:36 meumeu sshd[17360]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.103.132 Dec 2 06:53:38 meumeu sshd[17360]: Failed password for invalid user adm1n12 from 106.13.103.132 port 48350 ssh2 Dec 2 07:01:24 meumeu sshd[18421]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.103.132 ... |
2019-12-02 14:03:30 |
| 222.186.175.150 | attack | pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.150 user=root Failed password for root from 222.186.175.150 port 11662 ssh2 Failed password for root from 222.186.175.150 port 11662 ssh2 Failed password for root from 222.186.175.150 port 11662 ssh2 Failed password for root from 222.186.175.150 port 11662 ssh2 |
2019-12-02 14:16:48 |
| 175.158.50.19 | attackbots | Dec 2 01:01:25 plusreed sshd[23552]: Invalid user williamsburg from 175.158.50.19 ... |
2019-12-02 14:08:50 |
| 101.78.240.10 | attackbotsspam | 2019-12-02T05:31:16.834984shield sshd\[9696\]: Invalid user ann from 101.78.240.10 port 41116 2019-12-02T05:31:16.839790shield sshd\[9696\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.78.240.10 2019-12-02T05:31:18.987675shield sshd\[9696\]: Failed password for invalid user ann from 101.78.240.10 port 41116 ssh2 2019-12-02T05:39:00.725706shield sshd\[12003\]: Invalid user toniann from 101.78.240.10 port 53252 2019-12-02T05:39:00.730336shield sshd\[12003\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.78.240.10 |
2019-12-02 13:54:42 |
| 152.32.101.212 | attack | UTC: 2019-12-01 port: 23/tcp |
2019-12-02 14:15:03 |
| 46.229.168.138 | attackbotsspam | Attacks websites by trying to access known vulnerables of plugins, brute-force of backends or probing of administrative tools |
2019-12-02 13:48:58 |