IP address

Passive DNS

Tags: Scanner

IP blacklists

CI Army

64.89.163.133 is listed on the CI Army blacklist.

Description: Collective Intelligence Network Security is a Threat Intelligence<br>database that provides scores for IPs. Source of unspecified malicious attacks<br>most of them will be active attackers/scanners
Type of feed: primary (feed detail page)

Last checked at: 2026-01-31 03:50:00.985000
Was present on blacklist at: 2026-01-22 03:50, 2026-01-23 03:50, 2026-01-24 03:50, 2026-01-25 03:50, 2026-01-26 03:50, 2026-01-27 03:50, 2026-01-28 03:50, 2026-01-29 03:50, 2026-01-30 03:50, 2026-01-31 03:50

DShield Block

64.89.163.133 was recently listed on the DShield Block blacklist, but currently it is not.

Description: Recommended Block List by DShield.org. It summarizes the top 20 attacking<br>class C (/24) subnets over the last three days.
Type of feed: secondary (feed detail page)

Last checked at: 2026-04-06 04:50:00
Was present on blacklist at: 2026-01-23 04:50

AbuseIPDB

64.89.163.133 is listed on the AbuseIPDB blacklist.

Description: AbuseIPDB is a project managed by Marathon Studios Inc.<br>Lists IPs performing a malicious activity (DDoS, spam, phishing...)
Type of feed: primary (feed detail page)

Last checked at: 2026-03-28 05:00:00.605000
Was present on blacklist at: 2026-01-24 05:00, 2026-01-25 05:00, 2026-01-28 05:00, 2026-01-29 05:00, 2026-01-31 05:00, 2026-02-01 05:00, 2026-02-04 05:00, 2026-02-06 05:00, 2026-02-12 05:00, 2026-02-14 05:00, 2026-02-15 05:00, 2026-02-19 05:00, 2026-02-23 05:00, 2026-03-01 05:00, 2026-03-02 05:00, 2026-03-03 05:00, 2026-03-04 05:00, 2026-03-10 05:00, 2026-03-11 05:00, 2026-03-12 05:00, 2026-03-13 05:00, 2026-03-14 05:00, 2026-03-15 05:00, 2026-03-18 05:00, 2026-03-19 05:00, 2026-03-20 05:00, 2026-03-21 05:00, 2026-03-22 05:00, 2026-03-24 05:00, 2026-03-25 05:00, 2026-03-27 05:00, 2026-03-28 05:00

Spamhaus SBL

64.89.163.133 is listed on the Spamhaus SBL blacklist.

Description: The Spamhaus Block List ("SBL") Advisory is a database of IP addresses from which Spamhaus does not recommend the acceptance of electronic mail.
Type of feed: secondary (DNSBL) (feed detail page)

Last checked at: 2026-04-01 19:00:30.228000
Was present on blacklist at: 2026-01-28 19:00, 2026-02-04 19:00, 2026-02-11 19:00, 2026-02-18 19:00, 2026-02-25 19:00, 2026-03-04 19:00, 2026-03-11 19:00, 2026-03-18 19:00, 2026-03-25 19:00, 2026-04-01 19:00

Spamhaus DROP

64.89.163.133 is listed on the Spamhaus DROP blacklist.

Description: Spamhaus DROP (Don't Route Or Peer) list. Netblocks controlled by spammers or cyber criminals. The DROP lists are a tiny subset of the SBL, designed for use by firewalls and routing equipment to filter out the malicious traffic from these netblocks.
Type of feed: secondary (DNSBL) (feed detail page)

Last checked at: 2026-04-01 19:00:30.228000
Was present on blacklist at: 2026-01-28 19:00, 2026-02-04 19:00, 2026-02-11 19:00, 2026-02-18 19:00, 2026-02-25 19:00, 2026-03-04 19:00, 2026-03-11 19:00, 2026-03-18 19:00, 2026-03-25 19:00, 2026-04-01 19:00

Threat categories

TL	Role	Category	Details
70	src	scan	port: 5432
30	src	—

Warden events (676)

2026-04-06: ReconScanning (node.4dc198): 3; ReconScanning (node.368407): 5
2026-04-05: ReconScanning (node.368407): 3
2026-04-04: ReconScanning (node.4dc198): 3; ReconScanning (node.368407): 3
2026-04-03: ReconScanning (node.4dc198): 9; ReconScanning (node.368407): 3
2026-04-02: ReconScanning (node.368407): 7; ReconScanning (node.4dc198): 3
2026-04-01: ReconScanning (node.4dc198): 6; ReconScanning (node.368407): 6
2026-03-30: ReconScanning (node.368407): 8; ReconScanning (node.4dc198): 5; ReconScanning (node.ce2b59): 2
2026-03-29: ReconScanning (node.368407): 11
2026-03-28: ReconScanning (node.368407): 2
2026-03-27: ReconScanning (node.4dc198): 7; ReconScanning (node.368407): 6
2026-03-26: ReconScanning (node.368407): 6; ReconScanning (node.4dc198): 2
2026-03-25: ReconScanning (node.4dc198): 5; AnomalyTraffic (node.6a1878): 1; ReconScanning (node.368407): 5
2026-03-24: ReconScanning (node.4dc198): 4; ReconScanning (node.368407): 8
2026-03-23: ReconScanning (node.368407): 2; ReconScanning (node.4dc198): 2
2026-03-22: ReconScanning (node.4dc198): 11; ReconScanning (node.368407): 10; AnomalyTraffic (node.6a1878): 2
2026-03-21: ReconScanning (node.368407): 2; ReconScanning (node.4dc198): 1
2026-03-20: ReconScanning (node.368407): 12; ReconScanning (node.4dc198): 4
2026-03-19: ReconScanning (node.368407): 3
2026-03-18: ReconScanning (node.368407): 11
2026-03-17: ReconScanning (node.4dc198): 2; ReconScanning (node.368407): 7
2026-03-16: ReconScanning (node.368407): 1
2026-03-15: ReconScanning (node.368407): 8; ReconScanning (node.4dc198): 1
2026-03-14: ReconScanning (node.368407): 7; ReconScanning (node.4dc198): 2
2026-03-13: ReconScanning (node.4dc198): 1; ReconScanning (node.368407): 2
2026-03-12: ReconScanning (node.4dc198): 4; ReconScanning (node.368407): 3
2026-03-11: ReconScanning (node.368407): 2; ReconScanning (node.4dc198): 2
2026-03-10: ReconScanning (node.368407): 5; ReconScanning (node.4dc198): 2
2026-03-09: ReconScanning (node.4dc198): 2; ReconScanning (node.368407): 3
2026-03-08: ReconScanning (node.368407): 6
2026-03-07: ReconScanning (node.4dc198): 5; ReconScanning (node.368407): 4
2026-03-06: ReconScanning (node.4dc198): 5; ReconScanning (node.368407): 3
2026-03-05: ReconScanning (node.368407): 4; ReconScanning (node.4dc198): 4
2026-03-04: ReconScanning (node.368407): 4
2026-03-03: ReconScanning (node.368407): 16; ReconScanning (node.4dc198): 9
2026-03-02: ReconScanning (node.4dc198): 9; ReconScanning (node.368407): 11
2026-03-01: ReconScanning (node.368407): 8
2026-02-28: ReconScanning (node.368407): 15; ReconScanning (node.4dc198): 3
2026-02-27: ReconScanning (node.4dc198): 6; ReconScanning (node.368407): 5
2026-02-26: ReconScanning (node.368407): 17; ReconScanning (node.4dc198): 8
2026-02-25: ReconScanning (node.4dc198): 5; ReconScanning (node.368407): 2
2026-02-24: ReconScanning (node.4dc198): 5; ReconScanning (node.368407): 5
2026-02-23: ReconScanning (node.368407): 2; ReconScanning (node.4dc198): 2
2026-02-22: ReconScanning (node.4dc198): 2; ReconScanning (node.368407): 2
2026-02-21: ReconScanning (node.4dc198): 1; ReconScanning (node.368407): 6
2026-02-20: ReconScanning (node.368407): 6; ReconScanning (node.4dc198): 3
2026-02-19: ReconScanning (node.4dc198): 10; ReconScanning (node.368407): 9
2026-02-18: AnomalyTraffic (node.ffe95c): 1; ReconScanning (node.4dc198): 1; ReconScanning (node.368407): 7
2026-02-17: ReconScanning (node.4dc198): 5; ReconScanning (node.368407): 3
2026-02-16: ReconScanning (node.4dc198): 5; ReconScanning (node.368407): 4
2026-02-15: ReconScanning (node.368407): 3; ReconScanning (node.4dc198): 2; AnomalyTraffic (node.ffe95c): 1
2026-02-14: ReconScanning (node.4dc198): 3; ReconScanning (node.368407): 5
2026-02-13: ReconScanning (node.4dc198): 4; ReconScanning (node.368407): 2
2026-02-12: ReconScanning (node.4dc198): 8; ReconScanning (node.368407): 3
2026-02-11: ReconScanning (node.368407): 4; ReconScanning (node.4dc198): 6
2026-02-10: ReconScanning (node.4dc198): 4; ReconScanning (node.368407): 4
2026-02-09: ReconScanning (node.4dc198): 6; ReconScanning (node.368407): 4
2026-02-08: ReconScanning (node.368407): 2; ReconScanning (node.4dc198): 2
2026-02-06: ReconScanning (node.368407): 6
2026-02-05: ReconScanning (node.368407): 6
2026-02-04: ReconScanning (node.368407): 3; ReconScanning (node.4dc198): 2; AnomalyTraffic (node.ffe95c): 1
2026-02-03: ReconScanning (node.368407): 3; ReconScanning (node.4dc198): 6; AnomalyTraffic (node.ffe95c): 1
2026-02-02: ReconScanning (node.368407): 2; ReconScanning (node.4dc198): 1
2026-02-01: ReconScanning (node.4dc198): 6; ReconScanning (node.368407): 4; AnomalyTraffic (node.ffe95c): 3
2026-01-31: ReconScanning (node.4dc198): 3; ReconScanning (node.368407): 2; AnomalyTraffic (node.ffe95c): 2
2026-01-30: ReconScanning (node.4dc198): 8; ReconScanning (node.368407): 10; AnomalyTraffic (node.ffe95c): 1
2026-01-29: ReconScanning (node.368407): 1; AnomalyTraffic (node.ffe95c): 1; ReconScanning (node.4dc198): 2
2026-01-28: ReconScanning (node.4dc198): 3; ReconScanning (node.368407): 1; AnomalyTraffic (node.ffe95c): 1
2026-01-27: ReconScanning (node.4dc198): 6; AnomalyTraffic (node.ffe95c): 3; ReconScanning (node.368407): 1
2026-01-26: ReconScanning (node.368407): 3; AnomalyTraffic (node.ffe95c): 1; ReconScanning (node.4dc198): 5
2026-01-25: ReconScanning (node.368407): 6; AnomalyTraffic (node.ffe95c): 1; ReconScanning (node.4dc198): 4
2026-01-24: ReconScanning (node.4dc198): 8; ReconScanning (node.368407): 8; AnomalyTraffic (node.ffe95c): 3
2026-01-23: ReconScanning (node.368407): 6; AnomalyTraffic (node.ffe95c): 1; ReconScanning (node.4dc198): 4
2026-01-22: ReconScanning (node.368407): 3; ReconScanning (node.4dc198): 2
2026-01-21: ReconScanning (node.368407): 1; AnomalyTraffic (node.ffe95c): 1; ReconScanning (node.4dc198): 2

DShield reports (IP summary, reports)

2026-01-22: Number of reports: 20; Distinct targets: 20
2026-01-23: Number of reports: 50; Distinct targets: 39
2026-01-24: Number of reports: 50; Distinct targets: 39
2026-01-25: Number of reports: 112; Distinct targets: 74
2026-01-26: Number of reports: 112; Distinct targets: 74
2026-02-24: Number of reports: 76; Distinct targets: 60
2026-02-25: Number of reports: 76; Distinct targets: 60
2026-02-26: Number of reports: 53; Distinct targets: 31
2026-02-27: Number of reports: 44; Distinct targets: 33
2026-02-28: Number of reports: 72; Distinct targets: 49
2026-03-01: Number of reports: 72; Distinct targets: 50
2026-03-02: Number of reports: 54; Distinct targets: 34
2026-03-03: Number of reports: 68; Distinct targets: 38
2026-03-04: Number of reports: 73; Distinct targets: 49
2026-03-05: Number of reports: 73; Distinct targets: 49
2026-03-09: Number of reports: 97; Distinct targets: 59
2026-03-10: Number of reports: 118; Distinct targets: 71
2026-03-11: Number of reports: 80; Distinct targets: 47
2026-03-12: Number of reports: 67; Distinct targets: 40
2026-03-13: Number of reports: 67; Distinct targets: 40
2026-03-14: Number of reports: 74; Distinct targets: 50
2026-03-15: Number of reports: 74; Distinct targets: 43
2026-03-16: Number of reports: 74; Distinct targets: 47
2026-03-17: Number of reports: 57; Distinct targets: 36
2026-03-18: Number of reports: 101; Distinct targets: 46
2026-03-19: Number of reports: 122; Distinct targets: 70
2026-03-20: Number of reports: 60; Distinct targets: 43
2026-03-21: Number of reports: 77; Distinct targets: 49
2026-03-22: Number of reports: 77; Distinct targets: 45
2026-03-23: Number of reports: 90; Distinct targets: 62
2026-03-24: Number of reports: 90; Distinct targets: 62
2026-03-25: Number of reports: 100; Distinct targets: 53
2026-03-26: Number of reports: 100; Distinct targets: 53
2026-03-27: Number of reports: 41; Distinct targets: 29
2026-03-28: Number of reports: 47; Distinct targets: 29
2026-03-29: Number of reports: 47; Distinct targets: 29
2026-03-30: Number of reports: 97; Distinct targets: 62
2026-03-31: Number of reports: 97; Distinct targets: 62
2026-04-01: Number of reports: 61; Distinct targets: 41
2026-04-02: Number of reports: 56; Distinct targets: 44
2026-04-03: Number of reports: 109; Distinct targets: 71
2026-04-04: Number of reports: 73; Distinct targets: 37
2026-04-05: Number of reports: 84; Distinct targets: 66

OTX pulses

[6978bd03d8b34311571b03be] 2026-01-27 13:26:26.981000 | PostgresQL honeypot logs for 2026-01-27

Author name:	jnazario
Pulse modified:	2026-01-27 13:26:26.981000
Indicator created:	2026-01-27 13:26:27
Indicator role:	None
Indicator title:
Indicator expiration:	2026-02-26 13:00:00

[697e03110dc0e877e477e44d] 2026-01-31 13:26:41.912000 | PostgresQL honeypot logs for 2026-01-31

Author name:	jnazario
Pulse modified:	2026-01-31 13:26:41.912000
Indicator created:	2026-01-31 13:26:42
Indicator role:	None
Indicator title:
Indicator expiration:	2026-03-02 13:00:00

[6980a4d75b88d383bce4c1fc] 2026-02-02 13:21:27.526000 | PostgresQL honeypot logs for 2026-02-02

Author name:	jnazario
Pulse modified:	2026-02-02 13:21:27.526000
Indicator created:	2026-02-02 13:21:28
Indicator role:	None
Indicator title:
Indicator expiration:	2026-03-04 13:00:00

[698f251ba9abcdf8ff937505] 2026-02-13 13:20:27.442000 | PostgresQL honeypot logs for 2026-02-13

Author name:	jnazario
Pulse modified:	2026-02-13 13:20:27.442000
Indicator created:	2026-02-13 13:20:28
Indicator role:	None
Indicator title:
Indicator expiration:	2026-03-15 13:00:00

[6999b155944f3b50f522a99b] 2026-02-21 13:21:25.348000 | PostgresQL honeypot logs for 2026-02-21

Author name:	jnazario
Pulse modified:	2026-02-21 13:21:25.348000
Indicator created:	2026-02-21 13:21:26
Indicator role:	None
Indicator title:
Indicator expiration:	2026-03-23 13:00:00

Origin AS: AS401626 - NETIFACE-TORONTO
BGP Prefix: 64.89.163.0/24
hostname: (null)
Address block ('inetnum' or 'NetRange' in whois database): 64.89.160.0 - 64.89.163.255
last_activity: 2026-04-06 22:52:38
last_warden_event: 2026-04-06 22:52:38
rep: 0.6307907467796688
reserved_range: 0
Shodan's InternetDB: Open ports: 22; Tags: scanner; CPEs: cpe:/o:canonical:ubuntu_linux, cpe:/a:openbsd:openssh:8.2p1
ts_added: 2026-01-21 19:00:29.788000
ts_last_update: 2026-04-06 22:53:17.358000

Warden event timeline

DShield event timeline

Presence on blacklists

OTX pulses