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: United Kingdom of Great Britain and Northern Ireland (the)

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

;; QUESTION SECTION:
;45.133.125.154.			IN	A

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

;; Query time: 12 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 06 01:19:32 CST 2025
;; MSG SIZE  rcvd: 107
Host info
154.125.133.45.in-addr.arpa domain name pointer 45.133.125.154.g.network.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
154.125.133.45.in-addr.arpa	name = 45.133.125.154.g.network.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
209.17.96.90 attackbots
The IP has triggered Cloudflare WAF. CF-Ray: 56f71fc52a78e3aa | WAF_Rule_ID: ipr24 | WAF_Kind: firewall | CF_Action: challenge | Country: US | CF_IPClass: noRecord | Protocol: HTTP/1.1 | Method: GET | Host: lab.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-03-07 03:36:53
219.78.206.158 attackspambots
Honeypot attack, port: 5555, PTR: n219078206158.netvigator.com.
2020-03-07 03:38:39
125.64.94.211 attackbotsspam
125.64.94.211 was recorded 8 times by 7 hosts attempting to connect to the following ports: 5984,9200,27017,6379. Incident counter (4h, 24h, all-time): 8, 34, 10986
2020-03-07 03:36:25
108.53.139.181 attack
Scan detected and blocked 2020.03.06 14:29:27
2020-03-07 03:27:41
60.220.220.144 attackbots
Mar  6 14:29:46 MK-Soft-VM3 sshd[15763]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=60.220.220.144 
Mar  6 14:29:48 MK-Soft-VM3 sshd[15763]: Failed password for invalid user ubnt from 60.220.220.144 port 53785 ssh2
...
2020-03-07 03:08:23
125.64.94.220 attackbots
Mar  6 20:26:48 debian-2gb-nbg1-2 kernel: \[5781973.008008\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=125.64.94.220 DST=195.201.40.59 LEN=68 TOS=0x00 PREC=0x00 TTL=240 ID=54321 PROTO=UDP SPT=59336 DPT=32795 LEN=48
2020-03-07 03:27:27
181.215.114.240 attackspambots
Mar  6 15:15:43 vlre-nyc-1 sshd\[6610\]: Invalid user debian from 181.215.114.240
Mar  6 15:15:43 vlre-nyc-1 sshd\[6610\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=181.215.114.240
Mar  6 15:15:44 vlre-nyc-1 sshd\[6610\]: Failed password for invalid user debian from 181.215.114.240 port 32898 ssh2
Mar  6 15:19:18 vlre-nyc-1 sshd\[6674\]: Invalid user raju from 181.215.114.240
Mar  6 15:19:18 vlre-nyc-1 sshd\[6674\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=181.215.114.240
...
2020-03-07 03:22:07
89.133.103.216 attackbotsspam
Mar  6 18:30:40 vps691689 sshd[26961]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=89.133.103.216
Mar  6 18:30:41 vps691689 sshd[26961]: Failed password for invalid user nitish from 89.133.103.216 port 59214 ssh2
...
2020-03-07 03:14:41
80.82.77.245 attackspam
Mar  6 19:44:00 debian-2gb-nbg1-2 kernel: \[5779404.477445\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=80.82.77.245 DST=195.201.40.59 LEN=57 TOS=0x00 PREC=0x00 TTL=247 ID=54321 PROTO=UDP SPT=35261 DPT=136 LEN=37
2020-03-07 03:44:48
106.12.171.65 attackspam
$f2bV_matches
2020-03-07 03:28:44
14.253.149.48 attackspam
Unauthorised access (Mar  6) SRC=14.253.149.48 LEN=52 TTL=108 ID=20191 DF TCP DPT=445 WINDOW=8192 SYN
2020-03-07 03:18:44
82.64.129.178 attack
Mar  6 10:50:03 server sshd\[26904\]: Invalid user pi from 82.64.129.178
Mar  6 10:50:03 server sshd\[26904\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=82-64-129-178.subs.proxad.net 
Mar  6 10:50:04 server sshd\[26904\]: Failed password for invalid user pi from 82.64.129.178 port 40082 ssh2
Mar  6 22:13:31 server sshd\[19091\]: Invalid user tinkerware from 82.64.129.178
Mar  6 22:13:31 server sshd\[19091\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=82-64-129-178.subs.proxad.net 
...
2020-03-07 03:25:55
185.176.27.90 attackspam
ET DROP Dshield Block Listed Source group 1 - port: 48310 proto: TCP cat: Misc Attack
2020-03-07 03:20:13
183.140.64.231 attack
suspicious action Fri, 06 Mar 2020 10:29:45 -0300
2020-03-07 03:11:32
108.243.112.12 attackbotsspam
Scan detected and blocked 2020.03.06 14:29:00
2020-03-07 03:47:27

Recently Reported IPs

153.18.225.157 253.215.66.88 54.34.204.108 55.67.195.133
69.41.100.184 218.9.247.41 162.216.52.243 141.115.211.197
143.179.131.25 251.36.202.48 220.147.80.33 195.105.238.86
137.123.146.186 59.185.151.94 161.2.92.80 49.46.101.65
217.108.198.233 180.149.5.122 205.205.88.10 219.37.66.106