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: Hitachi

Region: Ibaraki

Country: Japan

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 <<>> 61.125.49.248
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 41426
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;61.125.49.248.			IN	A

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

;; Query time: 64 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Dec 28 08:17:13 CST 2021
;; MSG SIZE  rcvd: 106
Host info
248.49.125.61.in-addr.arpa domain name pointer g248.61-125-49.ppp.wakwak.ne.jp.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
248.49.125.61.in-addr.arpa	name = g248.61-125-49.ppp.wakwak.ne.jp.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
218.78.101.32 attack
2020-06-11 14:12:14,899 fail2ban.actions: WARNING [ssh] Ban 218.78.101.32
2020-06-12 01:11:00
176.122.188.154 attackspam
Invalid user admin1 from 176.122.188.154 port 43154
2020-06-12 01:13:27
45.143.223.178 attackbots
spam (f2b h2)
2020-06-12 01:15:58
139.99.238.48 attack
Tried sshing with brute force.
2020-06-12 00:41:43
31.41.135.120 attackspam
Jun 11 12:11:29 *** sshd[19480]: Invalid user admin from 31.41.135.120
2020-06-12 01:17:30
162.243.232.174 attack
firewall-block, port(s): 5786/tcp
2020-06-12 01:00:18
146.185.180.60 attackbots
(sshd) Failed SSH login from 146.185.180.60 (NL/Netherlands/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Jun 11 18:07:14 s1 sshd[19596]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=146.185.180.60  user=root
Jun 11 18:07:15 s1 sshd[19596]: Failed password for root from 146.185.180.60 port 46190 ssh2
Jun 11 18:20:43 s1 sshd[19930]: Invalid user monitor from 146.185.180.60 port 35127
Jun 11 18:20:46 s1 sshd[19930]: Failed password for invalid user monitor from 146.185.180.60 port 35127 ssh2
Jun 11 18:28:00 s1 sshd[20068]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=146.185.180.60  user=root
2020-06-12 00:51:00
120.131.14.125 attackspambots
SSH Bruteforce attack
2020-06-12 00:56:31
144.217.34.151 attackspambots
trying to access non-authorized port
2020-06-12 00:37:57
218.144.189.250 attack
Brute-force attempt banned
2020-06-12 01:02:45
218.92.0.208 attackspam
Jun 11 18:24:18 eventyay sshd[23475]: Failed password for root from 218.92.0.208 port 58094 ssh2
Jun 11 18:27:25 eventyay sshd[23556]: Failed password for root from 218.92.0.208 port 26940 ssh2
Jun 11 18:27:28 eventyay sshd[23556]: Failed password for root from 218.92.0.208 port 26940 ssh2
...
2020-06-12 01:03:03
67.198.180.98 attackspam
Honeypot attack, port: 445, PTR: 67.198.180.98.static.krypt.com.
2020-06-12 00:52:34
61.161.209.134 attack
'IP reached maximum auth failures for a one day block'
2020-06-12 01:15:07
59.61.83.118 attackbotsspam
Jun 11 17:42:36 plex sshd[16596]: Invalid user duhb from 59.61.83.118 port 59848
2020-06-12 01:09:07
124.253.53.66 attackbots
Honeypot attack, port: 81, PTR: PTR record not found
2020-06-12 01:08:07

Recently Reported IPs

214.139.1.199 59.2.177.88 136.249.66.157 93.117.26.23
152.44.47.120 200.108.227.248 141.202.89.138 95.65.154.68
33.25.238.112 217.167.16.212 48.155.203.24 71.204.41.40
190.102.251.77 57.85.168.155 119.186.71.234 166.142.102.48
36.34.230.144 203.205.24.76 197.183.173.60 158.18.75.111