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: Russian Federation

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

;; QUESTION SECTION:
;45.148.126.224.			IN	A

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

;; Query time: 58 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 13 17:34:58 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 224.126.148.45.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 224.126.148.45.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
139.198.191.217 attackbots
Jan  3 10:21:44 mail sshd\[1687\]: Invalid user test from 139.198.191.217
Jan  3 10:21:44 mail sshd\[1687\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.198.191.217
...
2020-01-04 03:51:51
209.17.96.114 attack
The IP has triggered Cloudflare WAF. CF-Ray: 54f18c36bf2fba46 | WAF_Rule_ID: ipr24 | WAF_Kind: firewall | CF_Action: challenge | Country: US | CF_IPClass: noRecord | Protocol: HTTP/1.1 | Method: GET | Host: blog.skk.moe | User-Agent: Mozilla/5.0 (compatible; Nimbostratus-Bot/v1.3.2; http://cloudsystemnetworks.com) | CF_DC: ATL. Report generated by Cloudflare-WAF-to-AbuseIPDB (https://github.com/SukkaW/Cloudflare-WAF-to-AbuseIPDB).
2020-01-04 03:30:49
49.206.202.172 attackbotsspam
Unauthorized connection attempt from IP address 49.206.202.172 on Port 445(SMB)
2020-01-04 03:18:32
112.206.225.82 attack
Automatic report - SSH Brute-Force Attack
2020-01-04 03:34:21
58.87.67.142 attackspam
Jan  3 16:55:15 nextcloud sshd\[20076\]: Invalid user lcg from 58.87.67.142
Jan  3 16:55:15 nextcloud sshd\[20076\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.87.67.142
Jan  3 16:55:17 nextcloud sshd\[20076\]: Failed password for invalid user lcg from 58.87.67.142 port 48138 ssh2
...
2020-01-04 03:19:47
178.62.19.13 attackbotsspam
Jan  3 18:15:57 XXX sshd[14322]: Invalid user trustguest from 178.62.19.13 port 58898
2020-01-04 03:41:30
185.40.4.94 attackbots
Proxy Scan
2020-01-04 03:31:13
185.156.73.52 attackspambots
01/03/2020-14:05:55.541608 185.156.73.52 Protocol: 6 ET SCAN NMAP -sS window 1024
2020-01-04 03:33:03
198.23.129.3 attack
$f2bV_matches
2020-01-04 03:27:47
203.113.25.6 attackspam
Tried sshing with brute force.
2020-01-04 03:35:52
106.13.45.131 attackbotsspam
Brute-force attempt banned
2020-01-04 03:52:14
42.81.122.86 attackspambots
01/03/2020-20:42:22.811660 42.81.122.86 Protocol: 6 ET CINS Active Threat Intelligence Poor Reputation IP group 41
2020-01-04 03:45:47
210.211.116.204 attackspambots
frenzy
2020-01-04 03:39:11
213.6.65.130 attack
20/1/3@10:47:19: FAIL: Alarm-Network address from=213.6.65.130
...
2020-01-04 03:25:51
222.82.250.4 attackspambots
Jan  3 15:15:23 lnxweb61 sshd[9367]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.82.250.4
2020-01-04 03:44:42

Recently Reported IPs

45.148.126.186 45.148.127.222 45.148.127.89 45.146.36.78
45.148.234.149 45.148.234.16 45.148.126.16 45.148.232.60
45.148.235.100 45.148.234.192 45.148.232.22 45.148.235.106
45.148.234.38 45.152.166.213 45.149.80.28 45.150.243.129
45.153.212.50 45.152.199.119 45.148.31.161 45.151.237.232