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: San Jose

Region: California

Country: United States

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:
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#


NetRange:       13.64.0.0 - 13.107.255.255
CIDR:           13.64.0.0/11, 13.104.0.0/14, 13.96.0.0/13
NetName:        MSFT
NetHandle:      NET-13-64-0-0-1
Parent:         NET13 (NET-13-0-0-0-0)
NetType:        Direct Allocation
OriginAS:       
Organization:   Microsoft Corporation (MSFT)
RegDate:        2015-03-26
Updated:        2021-12-14
Ref:            https://rdap.arin.net/registry/ip/13.64.0.0



OrgName:        Microsoft Corporation
OrgId:          MSFT
Address:        One Microsoft Way
City:           Redmond
StateProv:      WA
PostalCode:     98052
Country:        US
RegDate:        1998-07-10
Updated:        2025-06-10
Comment:        To report suspected security issues specific to traffic emanating from Microsoft online services, including the distribution of malicious content or other illicit or illegal material through a Microsoft online service, please submit reports to:
Comment:        * https://cert.microsoft.com.  
Comment:        
Comment:        For SPAM and other abuse issues, such as Microsoft Accounts, please contact:
Comment:        * abuse@microsoft.com.  
Comment:        
Comment:        To report security vulnerabilities in Microsoft products and services, please contact:
Comment:        * secure@microsoft.com.  
Comment:        
Comment:        For legal and law enforcement-related requests, please contact:
Comment:        * msndcc@microsoft.com
Comment:        
Comment:        For routing, peering or DNS issues, please 
Comment:        contact:
Comment:        * IOC@microsoft.com
Ref:            https://rdap.arin.net/registry/entity/MSFT


OrgRoutingHandle: CHATU3-ARIN
OrgRoutingName:   Chaturmohta, Somesh 
OrgRoutingPhone:  +1-425-882-8080 
OrgRoutingEmail:  someshch@microsoft.com
OrgRoutingRef:    https://rdap.arin.net/registry/entity/CHATU3-ARIN

OrgTechHandle: BEDAR6-ARIN
OrgTechName:   Bedard, Dawn 
OrgTechPhone:  +1-425-538-6637 
OrgTechEmail:  dabedard@microsoft.com
OrgTechRef:    https://rdap.arin.net/registry/entity/BEDAR6-ARIN

OrgTechHandle: IPHOS5-ARIN
OrgTechName:   IPHostmaster, IPHostmaster 
OrgTechPhone:  +1-425-538-6637 
OrgTechEmail:  iphostmaster@microsoft.com
OrgTechRef:    https://rdap.arin.net/registry/entity/IPHOS5-ARIN

OrgTechHandle: MRPD-ARIN
OrgTechName:   Microsoft Routing, Peering, and DNS
OrgTechPhone:  +1-425-882-8080 
OrgTechEmail:  IOC@microsoft.com
OrgTechRef:    https://rdap.arin.net/registry/entity/MRPD-ARIN

OrgAbuseHandle: MAC74-ARIN
OrgAbuseName:   Microsoft Abuse Contact
OrgAbusePhone:  +1-425-882-8080 
OrgAbuseEmail:  abuse@microsoft.com
OrgAbuseRef:    https://rdap.arin.net/registry/entity/MAC74-ARIN

OrgTechHandle: SINGH683-ARIN
OrgTechName:   Singh, Prachi 
OrgTechPhone:  +1-425-707-5601 
OrgTechEmail:  pracsin@microsoft.com
OrgTechRef:    https://rdap.arin.net/registry/entity/SINGH683-ARIN


#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 13.83.90.155
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 57999
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;13.83.90.155.			IN	A

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

;; Query time: 6 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Mar 28 20:31:49 CST 2026
;; MSG SIZE  rcvd: 105
Host info
Host 155.90.83.13.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 155.90.83.13.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
92.118.38.38 attackspambots
Dec  4 00:31:50 vmanager6029 postfix/smtpd\[19036\]: warning: unknown\[92.118.38.38\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Dec  4 00:32:24 vmanager6029 postfix/smtpd\[19036\]: warning: unknown\[92.118.38.38\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
2019-12-04 07:37:08
94.177.214.200 attackbots
Dec  3 23:51:32 dev0-dcde-rnet sshd[3310]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.177.214.200
Dec  3 23:51:34 dev0-dcde-rnet sshd[3310]: Failed password for invalid user sg1424guad12 from 94.177.214.200 port 51778 ssh2
Dec  3 23:56:50 dev0-dcde-rnet sshd[3321]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.177.214.200
2019-12-04 07:14:19
187.134.33.202 attackbotsspam
Unauthorized connection attempt from IP address 187.134.33.202 on Port 445(SMB)
2019-12-04 07:35:59
112.85.42.175 attackbots
2019-12-04T00:39:16.3840961240 sshd\[9194\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.175  user=root
2019-12-04T00:39:18.2221401240 sshd\[9194\]: Failed password for root from 112.85.42.175 port 30925 ssh2
2019-12-04T00:39:21.8400801240 sshd\[9194\]: Failed password for root from 112.85.42.175 port 30925 ssh2
...
2019-12-04 07:43:54
13.77.177.1 attackspam
3389BruteforceFW22
2019-12-04 07:26:21
45.55.190.106 attack
Dec  3 13:03:02 php1 sshd\[8370\]: Invalid user cap from 45.55.190.106
Dec  3 13:03:02 php1 sshd\[8370\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.55.190.106
Dec  3 13:03:04 php1 sshd\[8370\]: Failed password for invalid user cap from 45.55.190.106 port 47291 ssh2
Dec  3 13:08:18 php1 sshd\[8832\]: Invalid user dziawa from 45.55.190.106
Dec  3 13:08:18 php1 sshd\[8832\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.55.190.106
2019-12-04 07:09:24
49.234.79.176 attackbots
Dec  3 13:03:16 php1 sshd\[4284\]: Invalid user quintayvio from 49.234.79.176
Dec  3 13:03:16 php1 sshd\[4284\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.79.176
Dec  3 13:03:18 php1 sshd\[4284\]: Failed password for invalid user quintayvio from 49.234.79.176 port 32974 ssh2
Dec  3 13:09:58 php1 sshd\[5241\]: Invalid user code from 49.234.79.176
Dec  3 13:09:58 php1 sshd\[5241\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.79.176
2019-12-04 07:11:28
118.27.31.188 attackbotsspam
Dec  3 23:01:02 hcbbdb sshd\[16411\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=v118-27-31-188.hkbx.static.cnode.io  user=sshd
Dec  3 23:01:05 hcbbdb sshd\[16411\]: Failed password for sshd from 118.27.31.188 port 55828 ssh2
Dec  3 23:07:08 hcbbdb sshd\[17127\]: Invalid user spot from 118.27.31.188
Dec  3 23:07:08 hcbbdb sshd\[17127\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=v118-27-31-188.hkbx.static.cnode.io
Dec  3 23:07:11 hcbbdb sshd\[17127\]: Failed password for invalid user spot from 118.27.31.188 port 38524 ssh2
2019-12-04 07:17:21
222.186.175.169 attackspam
Dec  4 00:21:54 vpn01 sshd[16442]: Failed password for root from 222.186.175.169 port 27550 ssh2
Dec  4 00:22:07 vpn01 sshd[16442]: error: maximum authentication attempts exceeded for root from 222.186.175.169 port 27550 ssh2 [preauth]
...
2019-12-04 07:31:24
218.219.246.124 attack
SSH brute-force: detected 7 distinct usernames within a 24-hour window.
2019-12-04 07:29:30
181.40.66.136 attack
Unauthorized connection attempt from IP address 181.40.66.136 on Port 445(SMB)
2019-12-04 07:24:03
167.99.7.149 attack
$f2bV_matches
2019-12-04 07:24:19
210.177.54.141 attackbots
Dec  3 23:51:50 sso sshd[2597]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.177.54.141
Dec  3 23:51:53 sso sshd[2597]: Failed password for invalid user rafaelina from 210.177.54.141 port 58540 ssh2
...
2019-12-04 07:07:10
147.139.138.183 attackbotsspam
Dec  4 00:09:32 ns37 sshd[31226]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=147.139.138.183
Dec  4 00:09:32 ns37 sshd[31226]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=147.139.138.183
2019-12-04 07:16:50
207.154.211.36 attackspam
2019-12-03T23:48:51.357592ns386461 sshd\[28180\]: Invalid user marjorie from 207.154.211.36 port 51044
2019-12-03T23:48:51.362749ns386461 sshd\[28180\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=207.154.211.36
2019-12-03T23:48:52.920303ns386461 sshd\[28180\]: Failed password for invalid user marjorie from 207.154.211.36 port 51044 ssh2
2019-12-03T23:55:39.726693ns386461 sshd\[2011\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=207.154.211.36  user=root
2019-12-03T23:55:40.962541ns386461 sshd\[2011\]: Failed password for root from 207.154.211.36 port 45010 ssh2
...
2019-12-04 07:11:48

Recently Reported IPs

85.25.172.249 3.101.24.234 110.77.187.17 2606:4700:10::6816:2336
110.78.138.211 2606:4700:10::6816:2897 2606:4700:10::6814:6773 2606:4700:10::6816:1898
2606:4700:10::6814:6832 2606:4700:10::ac43:2155 2606:4700:10::6814:5909 121.230.89.156
161.73.51.229 185.185.80.40 241.98.47.127 194.150.84.242
156.207.26.125 110.77.226.19 2606:4700:10::6814:5887 2606:4700:10::6814:4754