Port 21022AMLFilter HTTPS
**21022/tcp** is the default HTTPS port for *AMLFilter*, a platform developed by *AMLFilter Inc.* intended for Anti-Money Laundering filtering operations. The port is primarily used by their amlf-engine-02 modules to facilitate secure, encrypted communication between clients and the AMLFilter server..
- transport
- tcp
- in transit
- encrypted
- assignment
- unofficial
- risk
- 4/10
- lookups
- 22,000
single transport
payload protected on the wire
used by convention
caution
rank 100 of 993 · top 10%
Technical Details
what runs on :21022AMLFilter is an anti-money-laundering platform that relies on protected communication channels for transmitting sensitive financial and compliance data. Port 21022 is configured as the default HTTPS interface on the AMLFilter amlf-engine-02 module, leveraging TLS encryption to secure data in transit. This port facilitates management operations, rule updates, suspicious activity reporting, and integrations with other compliance systems.
The underlying protocol on this port is HTTPS, built atop TCP, ensuring reliable, encrypted communication. Administrators access the system interface via web browsers or API calls directed to this port, conducting configuration, maintenance, and investigations. The use of a non-standard HTTPS port is a common practice to help avoid casual recon or simple attacks targeting the default port 443.
Because this port often handles highly sensitive compliance data, the integrity and security of the communication here are paramount. Deployment best practices recommend ensuring only trusted internal clients or secure external partners communicate over this port, and that strong TLS configurations are enforced.
Security Information
exposure of :21022risk score
4/ 10caution
worth attention. how exposed you are depends on configuration — don't leave it reachable from the internet without a reason.
web services averages 3.9 across 112 ports — this one sits 0.1 above.
in transit
encrypted
payloads are protected on the wire
assignment
unofficial
used by convention, not registered — what answers here varies by deployment
reachable over
tcp
every listening transport is another surface to filter at the edge
security overview
Common Vulnerabilities:
- Vulnerabilities related to outdated or misconfigured TLS/SSL libraries (e.g., supporting weak ciphers, deprecated SSL versions)
- Exposure due to lack of proper authentication or access controls, leading to unauthorized access
- Web application flaws such as injection attacks, CSRF, or XSS within the AMLFilter's HTTPS interface
- Credential harvesting if multi-factor authentication is not enforced
Mitigation Strategies:
- Regularly update the AMLFilter application and underlying web server software
- Enforce strong TLS configurations (TLS 1.2 or higher) and disable insecure cipher suites
- Implement strict access controls, such as IP whitelisting and strong authentication (preferably MFA)
- Monitor and audit access logs to detect unauthorized or suspicious access attempts
- Conduct regular security assessments and vulnerability scans against the HTTPS interface
Related Ports
the 8 most looked-up other ports in web services — 112 ports carry that label.
| port | service | risk | |||
|---|---|---|---|---|---|
| :8888 | Sun Answerbook & Alt HTTP | TCP | Web Services | caution | 123.9k |
| :8000 | Intel Remote Desktop / Alternate HTTP Port | TCP | Web Services | safe | 84.3k |
| :8888 | NewsEDGE | TCPUDP | Web Services | caution | 83.3k |
| :8888 | HTTP Alternative Port | TCP | Web Services | caution | 76.5k |
| :8888 | GNUmp3d Streaming HTTP | TCP | Web Services | caution | 76.3k |
| :9080 | Groove RPC | TCPUDP | Web Services | caution | 70.8k |
| :8881 | Atlasz Secure Server | TCP | Web Services | caution | 67.6k |
| :80 | HTTP | TCPUDP | Web Services | caution | 67.3k |
risk mix of the 8 listed
- safe13%
- caution88%
0 of 8 encrypted