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

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

;; QUESTION SECTION:
;149.171.42.47.			IN	A

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

;; Query time: 46 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 16 19:49:50 CST 2025
;; MSG SIZE  rcvd: 106
Host info
Host 47.42.171.149.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 47.42.171.149.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
103.97.125.49 attack
2019-07-20T15:41:22.957150abusebot-3.cloudsearch.cf sshd\[27728\]: Invalid user marco from 103.97.125.49 port 37718
2019-07-20 23:52:39
45.55.254.13 attack
Jul 20 17:29:50 eventyay sshd[2692]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.55.254.13
Jul 20 17:29:52 eventyay sshd[2692]: Failed password for invalid user pi from 45.55.254.13 port 33414 ssh2
Jul 20 17:34:31 eventyay sshd[3929]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.55.254.13
...
2019-07-21 00:48:32
184.105.139.120 attackbotsspam
3389BruteforceFW23
2019-07-20 23:57:35
114.234.216.135 attackspam
[Aegis] @ 2019-07-20 12:37:09  0100 -> Sendmail rejected message.
2019-07-21 00:21:12
185.143.221.186 attack
Jul 20 18:32:17 lumpi kernel: INPUT:DROP:SPAMHAUS_EDROP:IN=eth0 OUT= MAC=52:54:a2:01:a5:04:d2:74:7f:6e:37:e3:08:00 SRC=185.143.221.186 DST=172.31.1.100 LEN=40 TOS=0x00 PREC=0x00 TTL=244 ID=6027 PROTO=TCP SPT=41732 DPT=5193 WINDOW=1024 RES=0x00 SYN URGP=0 
...
2019-07-21 00:46:15
104.248.151.241 attack
Splunk® : Brute-Force login attempt on SSH:
Jul 20 12:02:32 testbed sshd[9651]: Connection closed by 104.248.151.241 port 43460 [preauth]
2019-07-21 00:27:11
202.137.134.40 attackbots
2 failed emails per dmarc_support@corp.mail.ru [Fri Jul 19 00:00:00 2019 GMT thru Sat Jul 20 00:00:00 2019 GMT]
2019-07-21 00:53:38
197.50.110.209 attackspam
1 failed email per dmarc_support@corp.mail.ru [Fri Jul 19 00:00:00 2019 GMT thru Sat Jul 20 00:00:00 2019 GMT]
2019-07-21 00:54:14
168.167.51.17 attack
5 failed emails per dmarc_support@corp.mail.ru [Fri Jul 19 00:00:00 2019 GMT thru Sat Jul 20 00:00:00 2019 GMT]
2019-07-21 00:58:32
185.176.27.18 attack
20.07.2019 15:45:10 Connection to port 62501 blocked by firewall
2019-07-21 00:15:58
200.69.70.30 attackspam
5 failed emails per dmarc_support@corp.mail.ru [Fri Jul 19 00:00:00 2019 GMT thru Sat Jul 20 00:00:00 2019 GMT]
2019-07-21 01:19:57
186.148.169.127 attackspambots
6 failed emails per dmarc_support@corp.mail.ru [Fri Jul 19 00:00:00 2019 GMT thru Sat Jul 20 00:00:00 2019 GMT]
2019-07-21 00:57:28
193.254.37.90 attackspambots
12 failed emails per dmarc_support@corp.mail.ru [Fri Jul 19 00:00:00 2019 GMT thru Sat Jul 20 00:00:00 2019 GMT]
2019-07-21 00:55:42
202.137.134.61 attack
10 failed emails per dmarc_support@corp.mail.ru [Fri Jul 19 00:00:00 2019 GMT thru Sat Jul 20 00:00:00 2019 GMT]
2019-07-21 00:52:49
92.53.65.129 attackbots
firewall-block, port(s): 3764/tcp
2019-07-21 00:08:57

Recently Reported IPs

221.124.45.18 251.242.128.140 248.46.8.172 32.232.106.244
220.97.128.198 221.28.200.116 4.92.249.92 139.62.234.2
157.163.75.204 4.43.58.67 206.175.88.138 211.41.165.186
146.37.144.10 46.45.182.1 75.168.216.205 74.153.186.242
148.22.207.132 188.37.148.147 155.168.227.155 115.255.79.130