Must be a valid IPv4 or IPv6 ip address, e.g. 127.0.0.1 or 2001:DB8:0:0:8:800:200C:417A
Basic Info

City: unknown

Region: unknown

Country: Singapore

Internet Service Provider: unknown

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:
No discussion about this IP yet. Click above link to make one.
Comments on same subnet:
IP Type Details Datetime
148.66.134.3 spamattack
"GET","\\/xmlrpc.php"
2023-08-08 19:41:22
148.66.134.85 attackspambots
May  1 22:05:44 srv-ubuntu-dev3 sshd[30273]: Invalid user dkc from 148.66.134.85
May  1 22:05:44 srv-ubuntu-dev3 sshd[30273]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.66.134.85
May  1 22:05:44 srv-ubuntu-dev3 sshd[30273]: Invalid user dkc from 148.66.134.85
May  1 22:05:46 srv-ubuntu-dev3 sshd[30273]: Failed password for invalid user dkc from 148.66.134.85 port 52150 ssh2
May  1 22:10:00 srv-ubuntu-dev3 sshd[31012]: Invalid user ts3server from 148.66.134.85
May  1 22:10:00 srv-ubuntu-dev3 sshd[31012]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.66.134.85
May  1 22:10:00 srv-ubuntu-dev3 sshd[31012]: Invalid user ts3server from 148.66.134.85
May  1 22:10:02 srv-ubuntu-dev3 sshd[31012]: Failed password for invalid user ts3server from 148.66.134.85 port 36192 ssh2
May  1 22:14:37 srv-ubuntu-dev3 sshd[31743]: Invalid user john from 148.66.134.85
...
2020-05-02 05:43:54
148.66.134.85 attack
Apr 17 11:33:34 lukav-desktop sshd\[10646\]: Invalid user git from 148.66.134.85
Apr 17 11:33:34 lukav-desktop sshd\[10646\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.66.134.85
Apr 17 11:33:37 lukav-desktop sshd\[10646\]: Failed password for invalid user git from 148.66.134.85 port 49992 ssh2
Apr 17 11:36:45 lukav-desktop sshd\[10775\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.66.134.85  user=root
Apr 17 11:36:47 lukav-desktop sshd\[10775\]: Failed password for root from 148.66.134.85 port 37496 ssh2
2020-04-17 18:14:52
148.66.134.85 attackbots
SSH Bruteforce attack
2020-04-16 21:25:30
148.66.134.226 attackspam
Apr 16 05:37:35 mail.srvfarm.net postfix/smtpd[2662907]: NOQUEUE: reject: RCPT from unknown[148.66.134.226]: 554 5.7.1 Service unavailable; Client host [148.66.134.226] blocked using zen.spamhaus.org; https://www.spamhaus.org/query/ip/148.66.134.226 / https://www.spamhaus.org/sbl/query/SBLCSS; from= to= proto=SMTP helo=
Apr 16 05:37:35 mail.srvfarm.net postfix/smtpd[2662907]: lost connection after RCPT from unknown[148.66.134.226]
Apr 16 05:37:38 mail.srvfarm.net postfix/smtpd[2662488]: NOQUEUE: reject: RCPT from unknown[148.66.134.226]: 554 5.7.1 Service unavailable; Client host [148.66.134.226] blocked using zen.spamhaus.org; https://www.spamhaus.org/query/ip/148.66.134.226 / https://www.spamhaus.org/sbl/query/SBLCSS; from= to= proto=SMTP helo=
Apr 16 05:37:38 mail.srvfarm.net postfix/smtpd[2662488]: lost connection after RCPT from unknown[148.66.134.226]
Apr 16 05:37:48 mail.srvfarm.net postfix/s
2020-04-16 12:41:36
148.66.134.85 attackbots
2020-04-16T02:28:55.311991centos sshd[20868]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.66.134.85
2020-04-16T02:28:55.304439centos sshd[20868]: Invalid user service from 148.66.134.85 port 46530
2020-04-16T02:28:56.951684centos sshd[20868]: Failed password for invalid user service from 148.66.134.85 port 46530 ssh2
...
2020-04-16 08:29:54
148.66.134.85 attack
Apr 15 23:16:42 debian sshd[12615]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.66.134.85 
Apr 15 23:16:44 debian sshd[12615]: Failed password for invalid user store from 148.66.134.85 port 39988 ssh2
Apr 15 23:20:22 debian sshd[12620]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.66.134.85
2020-04-16 04:17:23
148.66.134.85 attackbotsspam
Apr 11 11:44:59 vserver sshd\[25337\]: Failed password for root from 148.66.134.85 port 57466 ssh2Apr 11 11:50:02 vserver sshd\[25380\]: Invalid user buhler from 148.66.134.85Apr 11 11:50:04 vserver sshd\[25380\]: Failed password for invalid user buhler from 148.66.134.85 port 49284 ssh2Apr 11 11:54:19 vserver sshd\[25420\]: Invalid user install from 148.66.134.85
...
2020-04-11 18:29:30
148.66.134.85 attack
Apr  8 15:15:45 haigwepa sshd[31979]: Failed password for ftp from 148.66.134.85 port 36512 ssh2
...
2020-04-08 23:01:42
148.66.134.85 attack
SSH Invalid Login
2020-04-08 09:48:09
148.66.134.85 attackbots
Apr  5 23:48:41 lanister sshd[18031]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.66.134.85  user=root
Apr  5 23:48:44 lanister sshd[18031]: Failed password for root from 148.66.134.85 port 54410 ssh2
Apr  5 23:53:04 lanister sshd[18114]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.66.134.85  user=root
Apr  5 23:53:06 lanister sshd[18114]: Failed password for root from 148.66.134.85 port 39302 ssh2
2020-04-06 16:19:32
148.66.134.85 attackspambots
(sshd) Failed SSH login from 148.66.134.85 (SG/Singapore/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Apr  4 01:42:20 amsweb01 sshd[26780]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.66.134.85  user=root
Apr  4 01:42:22 amsweb01 sshd[26780]: Failed password for root from 148.66.134.85 port 34576 ssh2
Apr  4 01:56:31 amsweb01 sshd[28270]: Invalid user user from 148.66.134.85 port 56942
Apr  4 01:56:34 amsweb01 sshd[28270]: Failed password for invalid user user from 148.66.134.85 port 56942 ssh2
Apr  4 02:00:42 amsweb01 sshd[28672]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.66.134.85  user=root
2020-04-04 08:29:41
148.66.134.85 attackspambots
$f2bV_matches
2020-03-30 01:45:24
148.66.134.148 attackspambots
SSH login attempts.
2020-03-28 01:28:50
148.66.134.85 attack
Repeated brute force against a port
2020-03-26 20:24:26
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 148.66.134.129
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 63912
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;148.66.134.129.			IN	A

;; AUTHORITY SECTION:
.			398	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2022021702 1800 900 604800 86400

;; Query time: 22 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 12:43:00 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 129.134.66.148.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 129.134.66.148.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
37.59.229.31 attackbotsspam
Invalid user fnjoroge from 37.59.229.31 port 52640
2020-04-16 07:52:24
194.61.27.249 attackspam
04/15/2020-19:09:53.803260 194.61.27.249 Protocol: 6 ET SCAN NMAP -sS window 1024
2020-04-16 07:16:37
193.108.44.122 attack
scan r
2020-04-16 07:38:39
148.70.149.39 attackspam
(sshd) Failed SSH login from 148.70.149.39 (CN/China/-): 5 in the last 3600 secs
2020-04-16 07:46:14
216.180.105.236 attack
(From lothian.winifred@hotmail.com) If you’ve been online any amount of time, you’re most likely still struggling to make the money you want online…

Am I right?

Well, we’re confident to say that you’ve come to the right place.

You might be thinking… Why are we different from the thousands of so-called “expert marketers” out there?

For one, I have the power to read your mind. I know exactly why you’re struggling right now...

OK - maybe reading your mind is a bit far fetched.

But what I can tell you is this…

We’ve worked with over 45,000+ customers.

And if they were struggling, we noticed it always came down to ONE important factor…

=>> http://bit.ly/UnlTraffic

You don't need to work for anyone else.

You don't need to take orders from your boss.

And you don't need to take permission to take vacation or spend a day with family.

And this is not just talk, let me show you real PROOF…

=>> http://bit.ly/UnlTraffic

Cheers
2020-04-16 07:31:27
213.180.203.2 attackspam
[Thu Apr 16 03:23:14.156372 2020] [:error] [pid 27072:tid 140327109256960] [client 213.180.203.2:55152] [client 213.180.203.2] ModSecurity: Access denied with code 403 (phase 2). Pattern match "^[\\\\d.:]+$" at REQUEST_HEADERS:Host. [file "/etc/modsecurity/owasp-modsecurity-crs-3.2.0/rules/REQUEST-920-PROTOCOL-ENFORCEMENT.conf"] [line "696"] [id "920350"] [msg "Host header is a numeric IP address"] [data "103.27.207.197"] [severity "WARNING"] [ver "OWASP_CRS/3.2.0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-protocol"] [tag "OWASP_CRS"] [tag "OWASP_CRS/PROTOCOL_VIOLATION/IP_HOST"] [tag "WASCTC/WASC-21"] [tag "OWASP_TOP_10/A7"] [tag "PCI/6.5.10"] [hostname "103.27.207.197"] [uri "/"] [unique_id "XpdtMtf343qgl4K6QZWtSwAABGY"]
...
2020-04-16 07:27:41
181.123.9.3 attack
SSH Brute-Forcing (server1)
2020-04-16 07:18:06
51.83.42.185 attack
Invalid user camden from 51.83.42.185 port 42146
2020-04-16 07:49:29
36.67.63.9 attackspam
(sshd) Failed SSH login from 36.67.63.9 (ID/Indonesia/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Apr 15 23:13:57 amsweb01 sshd[24632]: Invalid user tests from 36.67.63.9 port 34120
Apr 15 23:13:59 amsweb01 sshd[24632]: Failed password for invalid user tests from 36.67.63.9 port 34120 ssh2
Apr 15 23:29:56 amsweb01 sshd[26760]: Invalid user zeyu from 36.67.63.9 port 36742
Apr 15 23:29:58 amsweb01 sshd[26760]: Failed password for invalid user zeyu from 36.67.63.9 port 36742 ssh2
Apr 15 23:34:32 amsweb01 sshd[27282]: Invalid user cdv from 36.67.63.9 port 39882
2020-04-16 07:15:35
94.25.8.218 attack
Unauthorised access (Apr 15) SRC=94.25.8.218 LEN=52 PREC=0x20 TTL=114 ID=23950 DF TCP DPT=445 WINDOW=8192 SYN
2020-04-16 07:27:22
162.243.129.130 attack
Port Scan: Events[1] countPorts[1]: 21 ..
2020-04-16 07:31:09
51.68.127.137 attackbotsspam
Apr 16 00:37:58 srv01 sshd[30171]: Invalid user kms from 51.68.127.137 port 49224
Apr 16 00:37:58 srv01 sshd[30171]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.68.127.137
Apr 16 00:37:58 srv01 sshd[30171]: Invalid user kms from 51.68.127.137 port 49224
Apr 16 00:38:00 srv01 sshd[30171]: Failed password for invalid user kms from 51.68.127.137 port 49224 ssh2
Apr 16 00:40:17 srv01 sshd[30434]: Invalid user joe from 51.68.127.137 port 40496
...
2020-04-16 07:48:16
182.75.33.14 attackspam
Apr 15 20:00:02 ws24vmsma01 sshd[117279]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.75.33.14
Apr 15 20:00:04 ws24vmsma01 sshd[117279]: Failed password for invalid user mingo from 182.75.33.14 port 2160 ssh2
...
2020-04-16 07:24:30
129.211.92.41 attackbots
Invalid user trevor from 129.211.92.41 port 49204
2020-04-16 07:36:03
181.48.155.149 attackspam
Invalid user ubuntu from 181.48.155.149 port 42356
2020-04-16 07:45:39

Recently Reported IPs

148.66.135.0 148.66.133.89 148.66.135.121 148.66.135.73
148.66.134.243 148.66.136.10 148.66.136.1 148.66.136.11
148.66.136.124 148.66.136.121 148.66.136.123 148.66.136.137
148.66.136.151 148.66.136.152 148.66.136.150 148.66.136.188
148.66.136.175 148.66.136.189 148.66.136.2 148.66.136.215