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
🇺🇸 38.12.30.95	23 Jan 2026	(CT) IP 38.12.30.95 (US/United States/-) found to have 2 connections; Ports: ; Direction: inout; Tr ... show more (CT) IP 38.12.30.95 (US/United States/-) found to have 2 connections; Ports: ; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 38.12.30.95:65108 -> 192.168.161.12:443 (TIME_WAIT) tcp: 38.12.30.95:65114 -> 192.168.161.12:443 (TIME_WAIT) show less	Port Scan
🇺🇸 38.12.30.96	23 Jan 2026	(CT) IP 38.12.30.96 (US/United States/-) found to have 2 connections; Ports: ; Direction: inout; Tr ... show more (CT) IP 38.12.30.96 (US/United States/-) found to have 2 connections; Ports: ; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 38.12.30.96:54854 -> 192.168.161.12:443 (TIME_WAIT) tcp: 38.12.30.96:54862 -> 192.168.161.12:443 (TIME_WAIT) show less	Port Scan
🇺🇸 34.63.36.209	23 Jan 2026	(CT) IP 34.63.36.209 (US/United States/209.36.63.34.bc.googleusercontent.com) found to have 2 connec ... show more (CT) IP 34.63.36.209 (US/United States/209.36.63.34.bc.googleusercontent.com) found to have 2 connections; Ports: *; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 34.63.36.209:58784 -> 192.168.161.12:443 (TIME_WAIT) tcp: 34.63.36.209:58796 -> 192.168.161.12:443 (TIME_WAIT) show less	Port Scan
🇷🇪 92.130.190.72	23 Jan 2026	(CT) IP 92.130.190.72 (FR/France/lfbn-reu-1-359-72.w92-130.abo.wanadoo.fr) found to have 5 connectio ... show more (CT) IP 92.130.190.72 (FR/France/lfbn-reu-1-359-72.w92-130.abo.wanadoo.fr) found to have 5 connections; Ports: *; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 92.130.190.72:52472 -> 192.168.161.12:443 (TIME_WAIT) tcp: 92.130.190.72:44706 -> 192.168.161.12:443 (TIME_WAIT) tcp: 92.130.190.72:52476 -> 192.168.161.12:443 (TIME_WAIT) tcp: 92.130.190.72:40748 -> 192.168.161.12:443 (TIME_WAIT) tcp: 92.130.190.72:44712 -> 192.168.161.12:443 (TIME_WAIT) show less	Port Scan
🇷🇪 154.67.148.25	23 Jan 2026	(CT) IP 154.67.148.25 (RE/Reunion/-) found to have 2 connections; Ports: ; Direction: inout; Trigge ... show more (CT) IP 154.67.148.25 (RE/Reunion/-) found to have 2 connections; Ports: ; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 154.67.148.25:51040 -> 192.168.161.12:443 (TIME_WAIT) tcp: 154.67.148.25:53014 -> 192.168.161.12:443 (ESTABLISHED) show less	Port Scan
🇷🇪 109.122.136.78	23 Jan 2026	(CT) IP 109.122.136.78 (FR/France/78.136.122.109.rev.sfr.net) found to have 2 connections; Ports: ; ... show more (CT) IP 109.122.136.78 (FR/France/78.136.122.109.rev.sfr.net) found to have 2 connections; Ports: ; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 109.122.136.78:43316 -> 192.168.161.12:443 (ESTABLISHED) tcp: 109.122.136.78:43308 -> 192.168.161.12:443 (FIN_WAIT2) show less	Port Scan
🇸🇬 114.119.130.31	23 Jan 2026	(CT) IP 114.119.130.31 (SG/Singapore/petalbot-114-119-130-31.petalsearch.com) found to have 2 connec ... show more (CT) IP 114.119.130.31 (SG/Singapore/petalbot-114-119-130-31.petalsearch.com) found to have 2 connections; Ports: *; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 114.119.130.31:24857 -> 192.168.161.12:443 (TIME_WAIT) tcp: 114.119.130.31:24859 -> 192.168.161.12:443 (TIME_WAIT) show less	Port Scan
🇺🇸 154.40.43.72	23 Jan 2026	(CT) IP 154.40.43.72 (US/United States/-) found to have 4 connections; Ports: ; Direction: inout; T ... show more (CT) IP 154.40.43.72 (US/United States/-) found to have 4 connections; Ports: ; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 154.40.43.72:64136 -> 192.168.161.12:443 (TIME_WAIT) tcp: 154.40.43.72:64131 -> 192.168.161.12:443 (TIME_WAIT) tcp: 154.40.43.72:64141 -> 192.168.161.12:443 (TIME_WAIT) tcp: 154.40.43.72:64137 -> 192.168.161.12:443 (TIME_WAIT) show less	Port Scan
🇸🇬 114.119.134.161	23 Jan 2026	(CT) IP 114.119.134.161 (SG/Singapore/petalbot-114-119-134-161.petalsearch.com) found to have 2 conn ... show more (CT) IP 114.119.134.161 (SG/Singapore/petalbot-114-119-134-161.petalsearch.com) found to have 2 connections; Ports: *; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 114.119.134.161:25975 -> 192.168.161.12:80 (TIME_WAIT) tcp: 114.119.134.161:25977 -> 192.168.161.12:80 (TIME_WAIT) show less	Port Scan
🇸🇬 114.119.135.229	23 Jan 2026	(CT) IP 114.119.135.229 (SG/Singapore/petalbot-114-119-135-229.petalsearch.com) found to have 4 conn ... show more (CT) IP 114.119.135.229 (SG/Singapore/petalbot-114-119-135-229.petalsearch.com) found to have 4 connections; Ports: *; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 114.119.135.229:41763 -> 192.168.161.12:443 (TIME_WAIT) tcp: 114.119.135.229:41767 -> 192.168.161.12:443 (TIME_WAIT) tcp: 114.119.135.229:41765 -> 192.168.161.12:443 (TIME_WAIT) tcp: 114.119.135.229:41769 -> 192.168.161.12:443 (TIME_WAIT) show less	Port Scan
🇿🇦 172.68.42.66	23 Jan 2026	(CT) IP 172.68.42.66 (ZA/South Africa/-) found to have 2 connections; Ports: ; Direction: inout; Tr ... show more (CT) IP 172.68.42.66 (ZA/South Africa/-) found to have 2 connections; Ports: ; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 172.68.42.66:11282 -> 192.168.161.12:443 (ESTABLISHED) tcp: 172.68.42.66:9327 -> 192.168.161.12:443 (TIME_WAIT) show less	Port Scan
🇿🇦 197.234.243.77	23 Jan 2026	(CT) IP 197.234.243.77 (ZA/South Africa/-) found to have 2 connections; Ports: ; Direction: inout; ... show more (CT) IP 197.234.243.77 (ZA/South Africa/-) found to have 2 connections; Ports: ; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 197.234.243.77:13763 -> 192.168.161.12:443 (TIME_WAIT) tcp: 197.234.243.77:10865 -> 192.168.161.12:443 (TIME_WAIT) show less	Port Scan
🇸🇬 114.119.141.9	23 Jan 2026	(CT) IP 114.119.141.9 (SG/Singapore/petalbot-114-119-141-9.petalsearch.com) found to have 2 connecti ... show more (CT) IP 114.119.141.9 (SG/Singapore/petalbot-114-119-141-9.petalsearch.com) found to have 2 connections; Ports: *; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 114.119.141.9:28067 -> 192.168.161.12:443 (SYN_RECV) tcp: 114.119.141.9:55667 -> 192.168.161.12:80 (TIME_WAIT) show less	Port Scan
🇸🇬 114.119.156.71	23 Jan 2026	(CT) IP 114.119.156.71 (SG/Singapore/petalbot-114-119-156-71.petalsearch.com) found to have 2 connec ... show more (CT) IP 114.119.156.71 (SG/Singapore/petalbot-114-119-156-71.petalsearch.com) found to have 2 connections; Ports: *; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 114.119.156.71:30003 -> 192.168.161.12:443 (SYN_RECV) tcp: 114.119.156.71:30001 -> 192.168.161.12:443 (TIME_WAIT) show less	Port Scan
🇷🇪 165.169.33.122	23 Jan 2026	(CT) IP 165.169.33.122 (RE/Reunion/165-169-33-122.zeop.re) found to have 2 connections; Ports: ; Di ... show more (CT) IP 165.169.33.122 (RE/Reunion/165-169-33-122.zeop.re) found to have 2 connections; Ports: ; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 165.169.33.122:62174 -> 192.168.161.12:443 (FIN_WAIT2) tcp: 165.169.33.122:62128 -> 192.168.161.12:443 (TIME_WAIT) show less	Port Scan
🇨🇳 101.91.110.35	23 Jan 2026	(CT) IP 101.91.110.35 (CN/China/-) found to have 2 connections; Ports: ; Direction: inout; Trigger: ... show more (CT) IP 101.91.110.35 (CN/China/-) found to have 2 connections; Ports: ; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 101.91.110.35:10983 -> 192.168.161.12:443 (TIME_WAIT) tcp: 101.91.110.35:24316 -> 192.168.161.12:80 (TIME_WAIT) show less	Port Scan
🇺🇸 66.220.149.26	23 Jan 2026	(CT) IP 66.220.149.26 (US/United States/fwdproxy-prn-026.fbsv.net) found to have 2 connections; Port ... show more (CT) IP 66.220.149.26 (US/United States/fwdproxy-prn-026.fbsv.net) found to have 2 connections; Ports: *; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 66.220.149.26:63284 -> 192.168.161.12:80 (TIME_WAIT) tcp: 66.220.149.26:63306 -> 192.168.161.12:80 (TIME_WAIT) show less	Port Scan
🇷🇪 77.143.4.133	23 Jan 2026	(CT) IP 77.143.4.133 (FR/France/133.4.143.77.rev.sfr.net) found to have 3 connections; Ports: ; Dir ... show more (CT) IP 77.143.4.133 (FR/France/133.4.143.77.rev.sfr.net) found to have 3 connections; Ports: ; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 77.143.4.133:58560 -> 192.168.161.12:443 (TIME_WAIT) tcp: 77.143.4.133:38242 -> 192.168.161.12:443 (ESTABLISHED) tcp: 77.143.4.133:39922 -> 192.168.161.12:443 (TIME_WAIT) show less	Port Scan
🇷🇪 80.12.250.221	23 Jan 2026	(CT) IP 80.12.250.221 (RE/Reunion/-) found to have 2 connections; Ports: ; Direction: inout; Trigge ... show more (CT) IP 80.12.250.221 (RE/Reunion/-) found to have 2 connections; Ports: ; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 80.12.250.221:12886 -> 192.168.161.12:443 (TIME_WAIT) tcp: 80.12.250.221:21257 -> 192.168.161.12:443 (ESTABLISHED) show less	Port Scan
🇺🇸 35.188.67.4	23 Jan 2026	(CT) IP 35.188.67.4 (US/United States/4.67.188.35.bc.googleusercontent.com) found to have 2 connecti ... show more (CT) IP 35.188.67.4 (US/United States/4.67.188.35.bc.googleusercontent.com) found to have 2 connections; Ports: *; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 35.188.67.4:37814 -> 192.168.161.12:443 (TIME_WAIT) tcp: 35.188.67.4:37830 -> 192.168.161.12:443 (TIME_WAIT) show less	Port Scan
🇷🇪 154.67.156.235	23 Jan 2026	(CT) IP 154.67.156.235 (RE/Reunion/-) found to have 2 connections; Ports: ; Direction: inout; Trigg ... show more (CT) IP 154.67.156.235 (RE/Reunion/-) found to have 2 connections; Ports: ; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 154.67.156.235:58090 -> 192.168.161.12:443 (FIN_WAIT1) tcp: 154.67.156.235:60535 -> 192.168.161.12:443 (TIME_WAIT) show less	Port Scan
🇷🇴 80.94.95.37	23 Jan 2026	(CT) IP 80.94.95.37 (HU/Hungary/-) found to have 2 connections; Ports: ; Direction: inout; Trigger: ... show more (CT) IP 80.94.95.37 (HU/Hungary/-) found to have 2 connections; Ports: ; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 80.94.95.37:4456 -> 192.168.161.12:443 (SYN_RECV) tcp: 80.94.95.37:55715 -> 192.168.161.12:80 (TIME_WAIT) show less	Port Scan
🇿🇦 197.234.242.197	23 Jan 2026	(CT) IP 197.234.242.197 (ZA/South Africa/-) found to have 2 connections; Ports: ; Direction: inout; ... show more (CT) IP 197.234.242.197 (ZA/South Africa/-) found to have 2 connections; Ports: ; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 197.234.242.197:10530 -> 192.168.161.12:443 (ESTABLISHED) tcp: 197.234.242.197:9250 -> 192.168.161.12:443 (TIME_WAIT) show less	Port Scan
🇸🇬 165.22.54.253	23 Jan 2026	(CT) IP 165.22.54.253 (SG/Singapore/-) found to have 2 connections; Ports: ; Direction: inout; Trig ... show more (CT) IP 165.22.54.253 (SG/Singapore/-) found to have 2 connections; Ports: ; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 165.22.54.253:35254 -> 192.168.161.12:443 (TIME_WAIT) tcp: 165.22.54.253:35268 -> 192.168.161.12:443 (TIME_WAIT) show less	Port Scan
🇸🇬 172.70.93.31	23 Jan 2026	(CT) IP 172.70.93.31 (SG/Singapore/-) found to have 2 connections; Ports: ; Direction: inout; Trigg ... show more (CT) IP 172.70.93.31 (SG/Singapore/-) found to have 2 connections; Ports: ; Direction: inout; Trigger: CT_LIMIT; Logs: tcp: 172.70.93.31:12360 -> 192.168.161.12:443 (TIME_WAIT) tcp: 172.70.93.31:13676 -> 192.168.161.12:443 (ESTABLISHED) show less	Port Scan