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

;; QUESTION SECTION:
;199.83.45.14.			IN	A

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

;; Query time: 36 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Feb 15 11:55:57 CST 2025
;; MSG SIZE  rcvd: 105
Host info
Host 14.45.83.199.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 14.45.83.199.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
81.171.85.147 attack
\[2019-10-04 18:41:43\] NOTICE\[1948\] chan_sip.c: Registration from '\' failed for '81.171.85.147:50825' - Wrong password
\[2019-10-04 18:41:43\] SECURITY\[2006\] res_security_log.c: SecurityEvent="InvalidPassword",EventTV="2019-10-04T18:41:43.139-0400",Severity="Error",Service="SIP",EventVersion="2",AccountID="17511",SessionID="0x7f1e1c02d9c8",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP/81.171.85.147/50825",Challenge="3748bfa3",ReceivedChallenge="3748bfa3",ReceivedHash="1f5e04f3653bb44af5f508efd371ae26"
\[2019-10-04 18:42:28\] NOTICE\[1948\] chan_sip.c: Registration from '\' failed for '81.171.85.147:59321' - Wrong password
\[2019-10-04 18:42:28\] SECURITY\[2006\] res_security_log.c: SecurityEvent="InvalidPassword",EventTV="2019-10-04T18:42:28.283-0400",Severity="Error",Service="SIP",EventVersion="2",AccountID="20975",SessionID="0x7f1e1c4d2348",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP/81.17
2019-10-05 07:03:05
77.247.109.31 attack
SIPVicious Scanner Detection, PTR: PTR record not found
2019-10-05 07:17:06
103.250.36.113 attack
fail2ban
2019-10-05 07:19:47
46.101.72.145 attackbots
2019-10-04T22:33:17.646450abusebot-6.cloudsearch.cf sshd\[12303\]: Invalid user Cyber123 from 46.101.72.145 port 36474
2019-10-05 06:51:14
179.127.180.26 attackspambots
400 BAD REQUEST
2019-10-05 06:54:22
51.91.193.116 attackbotsspam
Oct  4 11:21:57 web9 sshd\[8827\]: Invalid user Utilisateur!23 from 51.91.193.116
Oct  4 11:21:57 web9 sshd\[8827\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.91.193.116
Oct  4 11:21:59 web9 sshd\[8827\]: Failed password for invalid user Utilisateur!23 from 51.91.193.116 port 59154 ssh2
Oct  4 11:25:49 web9 sshd\[9419\]: Invalid user Photo@2017 from 51.91.193.116
Oct  4 11:25:49 web9 sshd\[9419\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.91.193.116
2019-10-05 07:11:15
186.15.120.237 attack
Attempt to attack host OS, exploiting network vulnerabilities, on 04-10-2019 21:25:19.
2019-10-05 06:45:02
92.118.38.37 attack
Oct  5 00:50:10 relay postfix/smtpd\[16250\]: warning: unknown\[92.118.38.37\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct  5 00:50:25 relay postfix/smtpd\[14451\]: warning: unknown\[92.118.38.37\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct  5 00:50:44 relay postfix/smtpd\[15455\]: warning: unknown\[92.118.38.37\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct  5 00:50:58 relay postfix/smtpd\[14451\]: warning: unknown\[92.118.38.37\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct  5 00:51:17 relay postfix/smtpd\[11351\]: warning: unknown\[92.118.38.37\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2019-10-05 06:53:30
2001:4802:7803:104:be76:4eff:fe20:21f4 attack
A user with IP addr 2001:4802:7803:104:be76:4eff:fe20:21f4 has been locked out from signing in or using the password recovery form for the following reason: Used an invalid username 'zzzzz' to try to sign in.
The duration of the lockout
User IP: 2001:4802:7803:104:be76:4eff:fe20:21f4
User hostname: 2001:4802:7803:104:be76:4eff:fe20:21f4
User location: United States
2019-10-05 07:04:13
197.47.113.196 attack
Attempt to attack host OS, exploiting network vulnerabilities, on 04-10-2019 21:25:20.
2019-10-05 06:43:50
128.106.195.126 attackbots
Invalid user braxton from 128.106.195.126 port 47337
2019-10-05 07:11:33
103.41.23.76 attackspambots
2019-10-04T23:01:08.869381abusebot-4.cloudsearch.cf sshd\[31603\]: Invalid user 123Secure from 103.41.23.76 port 53694
2019-10-05 07:20:47
191.252.195.141 attackbots
fail2ban
2019-10-05 06:50:25
206.189.204.63 attack
Oct  5 00:28:27 mail sshd\[4066\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.204.63  user=root
Oct  5 00:28:29 mail sshd\[4066\]: Failed password for root from 206.189.204.63 port 59506 ssh2
Oct  5 00:32:03 mail sshd\[4409\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.204.63  user=root
Oct  5 00:32:04 mail sshd\[4409\]: Failed password for root from 206.189.204.63 port 41898 ssh2
Oct  5 00:35:38 mail sshd\[4660\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.204.63  user=root
2019-10-05 06:55:51
91.217.0.72 attackbotsspam
Unauthorised access (Oct  4) SRC=91.217.0.72 LEN=44 TTL=245 ID=53036 DF TCP DPT=8080 WINDOW=14600 SYN
2019-10-05 07:23:31

Recently Reported IPs

133.135.111.29 145.79.208.98 248.252.55.71 27.4.144.92
194.120.154.66 49.186.28.57 98.75.215.142 36.135.156.50
136.184.11.21 39.79.25.70 130.56.249.224 88.117.4.207
191.81.167.36 41.4.110.229 38.8.175.10 91.243.111.247
98.32.131.218 179.113.73.154 135.163.34.2 205.201.227.241