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

;; QUESTION SECTION:
;71.254.57.104.			IN	A

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

;; Query time: 9 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Jan 24 02:10:39 CST 2025
;; MSG SIZE  rcvd: 106
Host info
104.57.254.71.in-addr.arpa domain name pointer pool-71-254-57-104.atclnj.east.verizon.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
104.57.254.71.in-addr.arpa	name = pool-71-254-57-104.atclnj.east.verizon.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
49.204.225.216 attack
Unauthorized connection attempt detected from IP address 49.204.225.216 to port 445
2020-01-01 18:12:33
177.193.93.228 attack
Automatic report - Port Scan Attack
2020-01-01 18:26:37
122.14.228.229 attack
Jan  1 10:49:26 mail sshd\[29743\]: Invalid user sv from 122.14.228.229
Jan  1 10:49:26 mail sshd\[29743\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.14.228.229
Jan  1 10:49:28 mail sshd\[29743\]: Failed password for invalid user sv from 122.14.228.229 port 45386 ssh2
...
2020-01-01 18:13:44
118.120.79.222 attackbots
Scanning
2020-01-01 18:07:24
117.71.9.108 attackspam
Scanning
2020-01-01 18:14:50
213.136.89.204 attackbotsspam
Dec 31 01:18:10 nbi-636 sshd[11985]: Invalid user gdm from 213.136.89.204 port 52018
Dec 31 01:18:12 nbi-636 sshd[11985]: Failed password for invalid user gdm from 213.136.89.204 port 52018 ssh2
Dec 31 01:18:12 nbi-636 sshd[11985]: Received disconnect from 213.136.89.204 port 52018:11: Bye Bye [preauth]
Dec 31 01:18:12 nbi-636 sshd[11985]: Disconnected from 213.136.89.204 port 52018 [preauth]
Dec 31 01:25:06 nbi-636 sshd[13232]: User r.r from 213.136.89.204 not allowed because not listed in AllowUsers
Dec 31 01:25:06 nbi-636 sshd[13232]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=213.136.89.204  user=r.r
Dec 31 01:25:09 nbi-636 sshd[13232]: Failed password for invalid user r.r from 213.136.89.204 port 47866 ssh2
Dec 31 01:25:09 nbi-636 sshd[13232]: Received disconnect from 213.136.89.204 port 47866:11: Bye Bye [preauth]
Dec 31 01:25:09 nbi-636 sshd[13232]: Disconnected from 213.136.89.204 port 47866 [preauth]
Dec 31 01:27:46 ........
-------------------------------
2020-01-01 18:36:07
139.59.4.145 attackbotsspam
Automatic report - Banned IP Access
2020-01-01 18:40:59
94.191.99.243 attackbotsspam
Automatic report - SSH Brute-Force Attack
2020-01-01 18:34:40
110.5.78.190 attackspam
1577859782 - 01/01/2020 07:23:02 Host: 110.5.78.190/110.5.78.190 Port: 445 TCP Blocked
2020-01-01 18:40:36
118.33.23.14 attack
Honeypot attack, port: 5555, PTR: PTR record not found
2020-01-01 18:36:53
120.228.188.240 attack
Scanning
2020-01-01 18:28:52
61.219.11.153 attackbots
Jan  1 10:45:04 debian-2gb-nbg1-2 kernel: \[131236.444813\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=61.219.11.153 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=25398 PROTO=TCP SPT=63207 DPT=53 WINDOW=1024 RES=0x00 SYN URGP=0
2020-01-01 18:23:13
123.22.14.130 attack
1577859808 - 01/01/2020 07:23:28 Host: 123.22.14.130/123.22.14.130 Port: 445 TCP Blocked
2020-01-01 18:25:10
106.12.221.86 attackspam
$f2bV_matches
2020-01-01 18:32:19
62.210.28.57 attack
\[2020-01-01 05:18:56\] SECURITY\[2857\] res_security_log.c: SecurityEvent="FailedACL",EventTV="2020-01-01T05:18:56.014-0500",Severity="Error",Service="SIP",EventVersion="1",AccountID="1011972592277524",SessionID="0x7f0fb4a5a908",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP/62.210.28.57/56114",ACLName="no_extension_match"
\[2020-01-01 05:23:00\] SECURITY\[2857\] res_security_log.c: SecurityEvent="FailedACL",EventTV="2020-01-01T05:23:00.008-0500",Severity="Error",Service="SIP",EventVersion="1",AccountID="11011972592277524",SessionID="0x7f0fb4aabfc8",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP/62.210.28.57/55328",ACLName="no_extension_match"
\[2020-01-01 05:27:04\] SECURITY\[2857\] res_security_log.c: SecurityEvent="FailedACL",EventTV="2020-01-01T05:27:04.257-0500",Severity="Error",Service="SIP",EventVersion="1",AccountID="21011972592277524",SessionID="0x7f0fb4a5a908",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP/62.210.28.57/53901",ACLName="no_e
2020-01-01 18:36:39

Recently Reported IPs

213.181.169.92 94.131.80.65 44.204.42.203 114.77.93.97
116.111.89.122 54.92.41.198 153.138.208.219 201.133.160.53
31.237.70.123 210.217.25.41 77.149.171.147 65.145.39.113
149.104.189.168 7.169.219.53 221.5.33.182 171.201.202.74
104.0.227.113 96.84.232.196 155.62.186.62 108.118.108.102