AbuseIPDB

JavaScript is disabled. Some features of this site may not work properly. For a smoother experience, please enable JavaScript in your browser settings.

User hodi.host , the webmaster of hodi.host, joined AbuseIPDB in May 2022 and has reported 5,083 IP addresses.

Standing (weight) is good.

INACTIVE USER WEBMASTER

IP	Date	Comment	Categories
🇸🇬 114.119.130.210	23 Jan 2026	(CT) IP 114.119.130.210 (SG/Singapore/petalbot-114-119-130-210.petalsearch.com) found to have 2 conn ... show more (CT) IP 114.119.130.210 (SG/Singapore/petalbot-114-119-130-210.petalsearch.com) found to have 2 connections; Ports: *; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 114.119.130.210:29147 -> 192.168.161.12:443 (TIME_WAIT) tcp: 114.119.130.210:29149 -> 192.168.161.12:443 (TIME_WAIT) show less	Port Scan
🇿🇦 197.234.243.105	23 Jan 2026	(CT) IP 197.234.243.105 (ZA/South Africa/-) found to have 2 connections; Ports: ; Direction: inout; ... show more (CT) IP 197.234.243.105 (ZA/South Africa/-) found to have 2 connections; Ports: ; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 197.234.243.105:12291 -> 192.168.161.12:443 (TIME_WAIT) tcp: 197.234.243.105:12600 -> 192.168.161.12:443 (ESTABLISHED) show less	Port Scan
🇳🇱 51.137.113.31	23 Jan 2026	(CT) IP 51.137.113.31 (NL/The Netherlands/-) found to have 2 connections; Ports: ; Direction: inout ... show more (CT) IP 51.137.113.31 (NL/The Netherlands/-) found to have 2 connections; Ports: ; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 51.137.113.31:59675 -> 192.168.161.12:443 (TIME_WAIT) tcp: 51.137.113.31:38867 -> 192.168.161.12:443 (TIME_WAIT) show less	Port Scan
🇷🇪 80.12.250.205	23 Jan 2026	(CT) IP 80.12.250.205 (RE/Reunion/-) found to have 2 connections; Ports: ; Direction: inout; Trigge ... show more (CT) IP 80.12.250.205 (RE/Reunion/-) found to have 2 connections; Ports: ; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 80.12.250.205:7215 -> 192.168.161.12:443 (TIME_WAIT) tcp: 80.12.250.205:6832 -> 192.168.161.12:443 (ESTABLISHED) show less	Port Scan
🇿🇦 172.69.112.184	23 Jan 2026	(CT) IP 172.69.112.184 (ZA/South Africa/-) found to have 2 connections; Ports: ; Direction: inout; ... show more (CT) IP 172.69.112.184 (ZA/South Africa/-) found to have 2 connections; Ports: ; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 172.69.112.184:13106 -> 192.168.161.12:443 (ESTABLISHED) tcp: 172.69.112.184:11940 -> 192.168.161.12:443 (TIME_WAIT) show less	Port Scan
🇺🇸 130.131.220.100	23 Jan 2026	(CT) IP 130.131.220.100 (US/United States/-) found to have 2 connections; Ports: ; Direction: inout ... show more (CT) IP 130.131.220.100 (US/United States/-) found to have 2 connections; Ports: ; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 130.131.220.100:35933 -> 192.168.161.12:443 (TIME_WAIT) tcp: 130.131.220.100:51363 -> 192.168.161.12:443 (TIME_WAIT) show less	Port Scan
🇺🇸 170.106.147.130	23 Jan 2026	(CT) IP 170.106.147.130 (US/United States/-) found to have 2 connections; Ports: ; Direction: inout ... show more (CT) IP 170.106.147.130 (US/United States/-) found to have 2 connections; Ports: ; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 170.106.147.130:59583 -> 192.168.161.12:443 (TIME_WAIT) tcp: 170.106.147.130:47977 -> 192.168.161.12:443 (TIME_WAIT) show less	Port Scan
🇺🇸 35.237.36.69	23 Jan 2026	(CT) IP 35.237.36.69 (US/United States/69.36.237.35.bc.googleusercontent.com) found to have 5 connec ... show more (CT) IP 35.237.36.69 (US/United States/69.36.237.35.bc.googleusercontent.com) found to have 5 connections; Ports: *; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 35.237.36.69:43080 -> 192.168.161.12:443 (TIME_WAIT) tcp: 35.237.36.69:43062 -> 192.168.161.12:443 (TIME_WAIT) tcp: 35.237.36.69:43130 -> 192.168.161.12:443 (TIME_WAIT) tcp: 35.237.36.69:43076 -> 192.168.161.12:443 (TIME_WAIT) tcp: 35.237.36.69:43116 -> 192.168.161.12:443 (TIME_WAIT) show less	Port Scan
🇺🇸 52.162.248.32	23 Jan 2026	(CT) IP 52.162.248.32 (US/United States/-) found to have 2 connections; Ports: ; Direction: inout; ... show more (CT) IP 52.162.248.32 (US/United States/-) found to have 2 connections; Ports: ; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 52.162.248.32:44371 -> 192.168.161.12:443 (TIME_WAIT) tcp: 52.162.248.32:58673 -> 192.168.161.12:443 (TIME_WAIT) show less	Port Scan
🇺🇸 43.153.0.227	23 Jan 2026	(CT) IP 43.153.0.227 (US/United States/-) found to have 2 connections; Ports: ; Direction: inout; T ... show more (CT) IP 43.153.0.227 (US/United States/-) found to have 2 connections; Ports: ; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 43.153.0.227:36169 -> 192.168.161.12:443 (TIME_WAIT) tcp: 43.153.0.227:43553 -> 192.168.161.12:443 (TIME_WAIT) show less	Port Scan
🇷🇪 139.26.150.99	23 Jan 2026	(CT) IP 139.26.150.99 (RE/Reunion/-) found to have 2 connections; Ports: ; Direction: inout; Trigge ... show more (CT) IP 139.26.150.99 (RE/Reunion/-) found to have 2 connections; Ports: ; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 139.26.150.99:57654 -> 192.168.161.12:443 (TIME_WAIT) tcp: 139.26.150.99:57675 -> 192.168.161.12:443 (TIME_WAIT) show less	Port Scan
🇩🇪 3.68.33.139	23 Jan 2026	(CT) IP 3.68.33.139 (DE/Germany/ec2-3-68-33-139.eu-central-1.compute.amazonaws.com) found to have 3 ... show more (CT) IP 3.68.33.139 (DE/Germany/ec2-3-68-33-139.eu-central-1.compute.amazonaws.com) found to have 3 connections; Ports: *; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 3.68.33.139:36542 -> 192.168.161.12:443 (TIME_WAIT) tcp: 3.68.33.139:36562 -> 192.168.161.12:443 (TIME_WAIT) tcp: 3.68.33.139:36550 -> 192.168.161.12:443 (TIME_WAIT) show less	Port Scan
🇷🇪 83.198.76.10	23 Jan 2026	(CT) IP 83.198.76.10 (FR/France/lfbn-reu-1-231-10.w83-198.abo.wanadoo.fr) found to have 2 connection ... show more (CT) IP 83.198.76.10 (FR/France/lfbn-reu-1-231-10.w83-198.abo.wanadoo.fr) found to have 2 connections; Ports: *; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 83.198.76.10:49576 -> 192.168.161.12:443 (TIME_WAIT) tcp: 83.198.76.10:42028 -> 192.168.161.12:443 (TIME_WAIT) show less	Port Scan
🇷🇪 154.67.114.72	23 Jan 2026	(CT) IP 154.67.114.72 (RE/Reunion/-) found to have 2 connections; Ports: ; Direction: inout; Trigge ... show more (CT) IP 154.67.114.72 (RE/Reunion/-) found to have 2 connections; Ports: ; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 154.67.114.72:49592 -> 192.168.161.12:443 (TIME_WAIT) tcp: 154.67.114.72:49590 -> 192.168.161.12:443 (TIME_WAIT) show less	Port Scan
🇺🇸 154.40.36.90	23 Jan 2026	(CT) IP 154.40.36.90 (US/United States/-) found to have 3 connections; Ports: ; Direction: inout; T ... show more (CT) IP 154.40.36.90 (US/United States/-) found to have 3 connections; Ports: ; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 154.40.36.90:65263 -> 192.168.161.12:443 (TIME_WAIT) tcp: 154.40.36.90:65258 -> 192.168.161.12:443 (TIME_WAIT) tcp: 154.40.36.90:65264 -> 192.168.161.12:443 (SYN_RECV) show less	Port Scan
🇫🇷 51.68.111.199	23 Jan 2026	(CT) IP 51.68.111.199 (FR/France/crawl-vhnyxq.mj12bot.com) found to have 4 connections; Ports: ; Di ... show more (CT) IP 51.68.111.199 (FR/France/crawl-vhnyxq.mj12bot.com) found to have 4 connections; Ports: ; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 51.68.111.199:30079 -> 192.168.161.12:443 (TIME_WAIT) tcp: 51.68.111.199:21775 -> 192.168.161.12:443 (TIME_WAIT) tcp: 51.68.111.199:23623 -> 192.168.161.12:443 (TIME_WAIT) tcp: 51.68.111.199:28839 -> 192.168.161.12:443 (TIME_WAIT) show less	Port Scan
🇺🇸 100.48.162.207	23 Jan 2026	(CT) IP 100.48.162.207 (US/United States/ec2-100-48-162-207.compute-1.amazonaws.com) found to have 4 ... show more (CT) IP 100.48.162.207 (US/United States/ec2-100-48-162-207.compute-1.amazonaws.com) found to have 4 connections; Ports: *; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 100.48.162.207:45616 -> 192.168.161.12:443 (TIME_WAIT) tcp: 100.48.162.207:25755 -> 192.168.161.12:443 (TIME_WAIT) tcp: 100.48.162.207:56289 -> 192.168.161.12:80 (TIME_WAIT) tcp: 100.48.162.207:43616 -> 192.168.161.12:80 (TIME_WAIT) show less	Port Scan
🇨🇳 153.35.209.71	23 Jan 2026	(CT) IP 153.35.209.71 (CN/China/sogouspider-153-35-209-71.crawl.sogou.com) found to have 3 connectio ... show more (CT) IP 153.35.209.71 (CN/China/sogouspider-153-35-209-71.crawl.sogou.com) found to have 3 connections; Ports: *; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 153.35.209.71:34578 -> 192.168.161.12:443 (ESTABLISHED) tcp: 153.35.209.71:34122 -> 192.168.161.12:443 (TIME_WAIT) tcp: 153.35.209.71:34124 -> 192.168.161.12:443 (ESTABLISHED) show less	Port Scan
🇿🇦 197.234.243.106	23 Jan 2026	(CT) IP 197.234.243.106 (ZA/South Africa/-) found to have 2 connections; Ports: ; Direction: inout; ... show more (CT) IP 197.234.243.106 (ZA/South Africa/-) found to have 2 connections; Ports: ; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 197.234.243.106:13093 -> 192.168.161.12:443 (TIME_WAIT) tcp: 197.234.243.106:11447 -> 192.168.161.12:443 (TIME_WAIT) show less	Port Scan
192.168.161.1	23 Jan 2026	(CT) IP 192.168.161.1 (hod-fw-141.exodata.lan) found to have 6 connections; Ports: ; Direction: ino ... show more (CT) IP 192.168.161.1 (hod-fw-141.exodata.lan) found to have 6 connections; Ports: ; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 192.168.161.1:29544 -> 192.168.161.12:80 (TIME_WAIT) tcp: 192.168.161.1:39349 -> 192.168.161.12:80 (TIME_WAIT) tcp: 192.168.161.1:25891 -> 192.168.161.12:443 (ESTABLISHED) tcp: 192.168.161.1:61226 -> 192.168.161.12:80 (TIME_WAIT) tcp: 192.168.161.1:27923 -> 192.168.161.12:443 (TIME_WAIT) tcp: 192.168.161.1:9494 -> 192.168.161.12:443 (TIME_WAIT) show less	Port Scan
🇿🇦 172.68.42.67	23 Jan 2026	(CT) IP 172.68.42.67 (ZA/South Africa/-) found to have 2 connections; Ports: ; Direction: inout; Tr ... show more (CT) IP 172.68.42.67 (ZA/South Africa/-) found to have 2 connections; Ports: ; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 172.68.42.67:11296 -> 192.168.161.12:443 (ESTABLISHED) tcp: 172.68.42.67:13942 -> 192.168.161.12:443 (TIME_WAIT) show less	Port Scan
🇺🇸 40.77.179.255	23 Jan 2026	(CT) IP 40.77.179.255 (US/United States/msnbot-40-77-179-255.search.msn.com) found to have 2 connect ... show more (CT) IP 40.77.179.255 (US/United States/msnbot-40-77-179-255.search.msn.com) found to have 2 connections; Ports: *; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 40.77.179.255:23172 -> 192.168.161.12:443 (ESTABLISHED) tcp: 40.77.179.255:23169 -> 192.168.161.12:443 (TIME_WAIT) show less	Port Scan
🇷🇪 139.26.145.132	23 Jan 2026	(CT) IP 139.26.145.132 (RE/Reunion/-) found to have 2 connections; Ports: ; Direction: inout; Trigg ... show more (CT) IP 139.26.145.132 (RE/Reunion/-) found to have 2 connections; Ports: ; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 139.26.145.132:61902 -> 192.168.161.12:443 (TIME_WAIT) tcp: 139.26.145.132:61903 -> 192.168.161.12:443 (TIME_WAIT) show less	Port Scan
🇺🇸 18.213.106.41	23 Jan 2026	(CT) IP 18.213.106.41 (US/United States/ec2-18-213-106-41.compute-1.amazonaws.com) found to have 4 c ... show more (CT) IP 18.213.106.41 (US/United States/ec2-18-213-106-41.compute-1.amazonaws.com) found to have 4 connections; Ports: *; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 18.213.106.41:55259 -> 192.168.161.12:80 (TIME_WAIT) tcp: 18.213.106.41:28212 -> 192.168.161.12:443 (TIME_WAIT) tcp: 18.213.106.41:25399 -> 192.168.161.12:80 (TIME_WAIT) tcp: 18.213.106.41:51073 -> 192.168.161.12:80 (TIME_WAIT) show less	Port Scan
🇺🇸 20.115.49.134	23 Jan 2026	(CT) IP 20.115.49.134 (US/United States/-) found to have 2 connections; Ports: ; Direction: inout; ... show more (CT) IP 20.115.49.134 (US/United States/-) found to have 2 connections; Ports: ; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 20.115.49.134:55731 -> 192.168.161.12:443 (TIME_WAIT) tcp: 20.115.49.134:39184 -> 192.168.161.12:443 (TIME_WAIT) show less	Port Scan