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: Seongnam-si

Region: Gyeonggi-do

Country: South Korea

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:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 112.148.3.221
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 56292
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;112.148.3.221.			IN	A

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

;; Query time: 20 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Aug 15 12:10:08 CST 2024
;; MSG SIZE  rcvd: 106
Host info
Host 221.3.148.112.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 221.3.148.112.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
198.252.105.21 attackbotsspam
MYH,DEF GET /wordpress/wp-admin/
2019-12-01 18:07:41
125.71.215.213 attackspam
2019-12-01T06:17:19.977596hub.schaetter.us sshd\[15142\]: Invalid user flaatten from 125.71.215.213 port 60924
2019-12-01T06:17:19.987929hub.schaetter.us sshd\[15142\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.71.215.213
2019-12-01T06:17:21.900371hub.schaetter.us sshd\[15142\]: Failed password for invalid user flaatten from 125.71.215.213 port 60924 ssh2
2019-12-01T06:26:02.900202hub.schaetter.us sshd\[15187\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.71.215.213  user=sshd
2019-12-01T06:26:04.943307hub.schaetter.us sshd\[15187\]: Failed password for sshd from 125.71.215.213 port 37666 ssh2
...
2019-12-01 18:24:00
82.221.105.7 attackbots
400 BAD REQUEST
2019-12-01 18:13:16
222.186.175.155 attackspam
Repeated brute force against a port
2019-12-01 17:59:52
150.109.52.25 attack
Dec  1 10:59:30 lnxded63 sshd[5557]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=150.109.52.25
2019-12-01 18:16:34
210.71.232.236 attack
Dec  1 03:26:39 ws22vmsma01 sshd[217710]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.71.232.236
Dec  1 03:26:40 ws22vmsma01 sshd[217710]: Failed password for invalid user sugiura from 210.71.232.236 port 34092 ssh2
...
2019-12-01 18:00:23
209.17.96.202 attack
209.17.96.202 was recorded 8 times by 7 hosts attempting to connect to the following ports: 3389,5632,5351,5443,9983,30303,10443,44818. Incident counter (4h, 24h, all-time): 8, 60, 1225
2019-12-01 18:18:19
52.4.162.61 attackbotsspam
Triggered by Fail2Ban at Vostok web server
2019-12-01 17:53:11
95.85.26.23 attackspambots
Dec  1 06:29:22 firewall sshd[30431]: Invalid user server from 95.85.26.23
Dec  1 06:29:24 firewall sshd[30431]: Failed password for invalid user server from 95.85.26.23 port 43194 ssh2
Dec  1 06:37:17 firewall sshd[30676]: Invalid user somei from 95.85.26.23
...
2019-12-01 18:20:46
59.36.132.240 attack
Bad bot/spoofed identity
2019-12-01 18:08:44
81.43.31.205 attackbotsspam
UTC: 2019-11-30 port: 23/tcp
2019-12-01 18:19:38
112.64.170.178 attack
SSH Brute-Force reported by Fail2Ban
2019-12-01 18:07:12
45.237.239.52 attack
UTC: 2019-11-30 port: 23/tcp
2019-12-01 18:05:00
118.161.170.133 attackbots
UTC: 2019-11-30 port: 23/tcp
2019-12-01 18:15:40
182.71.108.154 attackspambots
fail2ban
2019-12-01 17:56:42

Recently Reported IPs

112.148.142.50 112.148.132.35 112.148.133.143 112.148.119.192
112.147.98.242 112.148.109.113 112.148.105.134 112.147.71.4
112.147.90.243 112.149.129.136 112.148.172.76 112.148.95.131
112.148.203.114 112.148.141.54 112.147.5.10 112.148.124.205
112.147.41.206 112.147.33.58 112.148.115.206 112.148.202.22