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

Region: Zug

Country: Switzerland

Internet Service Provider: Swisscom

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

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;213.200.195.129.		IN	A

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

;; Query time: 110 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Oct 30 02:14:02 CST 2019
;; MSG SIZE  rcvd: 119
Host info
129.195.200.213.in-addr.arpa domain name pointer 129.195.200.213.static.wline.lns.sme.cust.swisscom.ch.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
129.195.200.213.in-addr.arpa	name = 129.195.200.213.static.wline.lns.sme.cust.swisscom.ch.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
203.129.113.142 attackbots
[ThuAug0810:34:25.1029752019][:error][pid19312:tid139738456672000][client203.129.113.142:56557][client203.129.113.142]ModSecurity:Accessdeniedwithcode403\(phase2\).Patternmatch"\(\?:\$mozilla\^\|mozilla/[45]\\\\\\\\.[1-9]\|\^mozilla/4\\\\\\\\.0\$\)"atREQUEST_HEADERS:User-Agent.[file"/usr/local/apache.ea3/conf/modsec_rules/20_asl_useragents.conf"][line"419"][id"330131"][rev"3"][msg"Atomicorp.comWAFRules:MaliciousBotBlocked\(FakeMozillaUserAgentStringDetected\)"][severity"CRITICAL"][hostname"rs-solution.ch"][uri"/css/css.php"][unique_id"XUvekbMkYla6CB-jB4KUkQAAAEM"]\,referer:rs-solution.ch[ThuAug0810:34:28.8842582019][:error][pid473:tid139738245707520][client203.129.113.142:54460][client203.129.113.142]ModSecurity:Accessdeniedwithcode403\(phase2\).Patternmatch"\(\?:\$mozilla\^\|mozilla/[45]\\\\\\\\.[1-9]\|\^mozilla/4\\\\\\\\.0\$\)"atREQUEST_HEADERS:User-Agent.[file"/usr/local/apache.ea3/conf/modsec_rules/20_asl_useragents.conf"][line"419"][id"330131"][rev"3"][msg"Atomicorp.comWAFR
2019-08-08 20:09:02
95.167.78.26 attack
08/08/2019-08:17:16.867291 95.167.78.26 Protocol: 6 ET SCAN NMAP -sS window 1024
2019-08-08 20:21:55
213.74.203.106 attackbotsspam
Aug  8 12:10:36 MK-Soft-VM6 sshd\[24580\]: Invalid user lokesh from 213.74.203.106 port 47776
Aug  8 12:10:36 MK-Soft-VM6 sshd\[24580\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=213.74.203.106
Aug  8 12:10:38 MK-Soft-VM6 sshd\[24580\]: Failed password for invalid user lokesh from 213.74.203.106 port 47776 ssh2
...
2019-08-08 20:19:29
122.61.50.236 attackspambots
Sniffing for wp-login
2019-08-08 19:55:26
73.62.149.46 attackspam
Forbidden directory scan :: 2019/08/08 12:08:53 [error] 1106#1106: *1781912 access forbidden by rule, client: 73.62.149.46, server: [censored_1], request: "GET /knowledge-base/tech-tips-tricks/how-to-replace-character-with-new-line-using-notepad/.json HTTP/1.1", host: "www.[censored_1]", referrer: "https://www.[censored_1]/knowledge-base/tech-tips-tricks/how-to-replace-character-with-new-line-using-notepad/"
2019-08-08 19:52:20
31.130.203.85 attack
(From micgytyhaelsople@gmail.com) There is an wonderful  disposition after win. drrushin.com  http://rontisarligh.tk/3iyd8
2019-08-08 19:41:13
178.128.87.175 attackspambots
firewall-block, port(s): 2022/tcp
2019-08-08 20:28:15
106.75.67.14 attack
port scan and connect, tcp 5432 (postgresql)
2019-08-08 20:25:40
27.74.175.52 attackbots
Automatic report - Port Scan Attack
2019-08-08 20:16:15
218.92.0.178 attackbots
Aug  8 05:10:50 cac1d2 sshd\[31197\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.178  user=root
Aug  8 05:10:52 cac1d2 sshd\[31197\]: Failed password for root from 218.92.0.178 port 11637 ssh2
Aug  8 05:10:55 cac1d2 sshd\[31197\]: Failed password for root from 218.92.0.178 port 11637 ssh2
...
2019-08-08 20:11:34
51.77.157.78 attack
Automatic report - Banned IP Access
2019-08-08 20:05:22
69.165.239.85 attack
Multiple SSH auth failures recorded by fail2ban
2019-08-08 20:20:01
112.85.42.179 attackbots
2019-08-08T14:10:51.549141lon01.zurich-datacenter.net sshd\[14393\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.179  user=root
2019-08-08T14:10:53.417037lon01.zurich-datacenter.net sshd\[14393\]: Failed password for root from 112.85.42.179 port 51142 ssh2
2019-08-08T14:11:03.051070lon01.zurich-datacenter.net sshd\[14393\]: Failed password for root from 112.85.42.179 port 51142 ssh2
2019-08-08T14:11:05.973734lon01.zurich-datacenter.net sshd\[14393\]: Failed password for root from 112.85.42.179 port 51142 ssh2
2019-08-08T14:11:09.646207lon01.zurich-datacenter.net sshd\[14393\]: Failed password for root from 112.85.42.179 port 51142 ssh2
...
2019-08-08 20:15:29
185.101.231.42 attackbots
SSH Brute Force, server-1 sshd[16601]: Failed password for lp from 185.101.231.42 port 38150 ssh2
2019-08-08 20:08:40
178.128.255.8 attackspam
Aug  8 13:10:38 xeon sshd[49315]: Failed password for invalid user minecraft from 178.128.255.8 port 39938 ssh2
2019-08-08 19:39:55

Recently Reported IPs

16.34.71.189 41.33.129.44 60.168.185.147 173.217.198.118
98.184.221.216 114.236.194.120 233.254.123.122 80.156.141.46
208.16.52.158 194.230.239.203 50.11.13.57 114.233.161.248
129.70.133.55 170.200.238.38 138.226.179.13 128.3.233.194
92.5.88.158 61.21.12.188 27.150.151.151 151.109.253.140