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

;; QUESTION SECTION:
;99.45.92.98.			IN	A

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

;; Query time: 58 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 21 00:24:41 CST 2025
;; MSG SIZE  rcvd: 104
Host info
98.92.45.99.in-addr.arpa domain name pointer 99-45-92-98.lightspeed.knvltn.sbcglobal.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
98.92.45.99.in-addr.arpa	name = 99-45-92-98.lightspeed.knvltn.sbcglobal.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
129.158.73.144 attackspambots
Dec  3 17:25:52 icinga sshd[31793]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.158.73.144
Dec  3 17:25:54 icinga sshd[31793]: Failed password for invalid user pcsupport from 129.158.73.144 port 16775 ssh2
...
2019-12-04 01:17:33
112.85.42.180 attackbotsspam
Dec  1 13:45:25 microserver sshd[17648]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.180  user=root
Dec  1 13:45:27 microserver sshd[17648]: Failed password for root from 112.85.42.180 port 56190 ssh2
Dec  1 13:45:30 microserver sshd[17648]: Failed password for root from 112.85.42.180 port 56190 ssh2
Dec  1 13:45:34 microserver sshd[17648]: Failed password for root from 112.85.42.180 port 56190 ssh2
Dec  1 18:08:42 microserver sshd[39955]: Failed none for root from 112.85.42.180 port 40476 ssh2
Dec  1 18:08:43 microserver sshd[39955]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.180  user=root
Dec  1 18:08:45 microserver sshd[39955]: Failed password for root from 112.85.42.180 port 40476 ssh2
Dec  1 18:08:49 microserver sshd[39955]: Failed password for root from 112.85.42.180 port 40476 ssh2
Dec  1 18:08:53 microserver sshd[39955]: Failed password for root from 112.85.42.180 port 40476 ssh2
Dec  2 04:08:
2019-12-04 01:31:52
150.109.106.224 attackspam
Dec  3 16:58:44 markkoudstaal sshd[11498]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=150.109.106.224
Dec  3 16:58:47 markkoudstaal sshd[11498]: Failed password for invalid user jue from 150.109.106.224 port 41008 ssh2
Dec  3 17:05:08 markkoudstaal sshd[12181]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=150.109.106.224
2019-12-04 01:09:39
203.217.1.13 attackbots
12/03/2019-15:28:36.534446 203.217.1.13 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2019-12-04 01:08:32
222.186.175.167 attack
Triggered by Fail2Ban at Ares web server
2019-12-04 01:07:01
218.92.0.134 attackbots
Dec  3 18:15:28 fr01 sshd[29912]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.134  user=root
Dec  3 18:15:30 fr01 sshd[29912]: Failed password for root from 218.92.0.134 port 56102 ssh2
...
2019-12-04 01:32:49
143.0.165.135 attack
scan z
2019-12-04 01:03:44
129.226.160.122 attack
Dec  3 18:16:47 legacy sshd[30645]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.226.160.122
Dec  3 18:16:49 legacy sshd[30645]: Failed password for invalid user ullmann from 129.226.160.122 port 44946 ssh2
Dec  3 18:23:11 legacy sshd[30894]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.226.160.122
...
2019-12-04 01:24:04
82.64.189.69 attack
Automatic report - Port Scan Attack
2019-12-04 01:02:21
40.78.133.79 attack
Repeated brute force against a port
2019-12-04 01:18:22
86.105.53.166 attackbotsspam
2019-12-03T16:48:24.023422abusebot-3.cloudsearch.cf sshd\[7998\]: Invalid user admin from 86.105.53.166 port 33107
2019-12-04 01:08:00
106.52.22.202 attack
Dec  3 14:21:16 yesfletchmain sshd\[24084\]: Invalid user guest from 106.52.22.202 port 51978
Dec  3 14:21:16 yesfletchmain sshd\[24084\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.52.22.202
Dec  3 14:21:19 yesfletchmain sshd\[24084\]: Failed password for invalid user guest from 106.52.22.202 port 51978 ssh2
Dec  3 14:28:22 yesfletchmain sshd\[24217\]: Invalid user rudziah from 106.52.22.202 port 54602
Dec  3 14:28:22 yesfletchmain sshd\[24217\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.52.22.202
...
2019-12-04 01:17:58
183.99.77.161 attackbotsspam
2019-12-03T14:59:47.414223abusebot-4.cloudsearch.cf sshd\[25250\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.99.77.161  user=root
2019-12-04 01:23:34
218.1.18.78 attack
2019-12-03T16:43:12.058286abusebot-4.cloudsearch.cf sshd\[26009\]: Invalid user hansler from 218.1.18.78 port 30254
2019-12-04 00:55:59
41.204.161.217 attack
Sql/code injection probe
2019-12-04 00:55:12

Recently Reported IPs

251.177.86.211 250.81.221.67 200.62.162.91 94.235.159.37
168.15.2.118 80.140.87.70 172.111.38.108 129.52.75.167
42.171.134.154 35.185.132.240 62.30.250.191 202.171.82.48
2.141.88.176 43.154.94.122 238.5.190.187 215.88.168.136
58.240.75.27 32.14.104.64 43.60.180.156 246.238.90.125