Classification Unavailable
We analyzed ift.tt but could not definitively identify its purpose. However, you can launch a real-time deep scan to uncover hidden threats on any specific URL.
Low Confidence Result
Automated classification did not meet our strict confidence standards for this domain.
Real-Time Investigation
If you encountered a link from this domain, run a real-time investigation to analyze its current content.
Powered by URLert
Recent Threat Analysis
URLert analyzed recent scan activity for ift.tt and found 1 result.
| Status | Target URL | Type | Time |
|---|---|---|---|
| Safe | https://ift.tt/1Ax6X0Y | 1w ago |
Network Infrastructure
Historical and current IP address mappings for this domain.
| IP Address / Infrastructure | Status | Subdomains | Last Seen |
|---|---|---|---|
AMAZON-02 - Amazon.com, Inc. (AS16509) | Historical | ift.tt | 1 day ago |
AMAZON-02 - Amazon.com, Inc. (AS16509) | Historical | ift.tt | 1 day ago |
AMAZON-02 - Amazon.com, Inc. (AS16509) | Historical | ift.tt | 1 day ago |
AMAZON-02 - Amazon.com, Inc. (AS16509) | Historical | ift.tt | 1 day ago |
AMAZON-02 - Amazon.com, Inc. (AS16509) | Active | ift.tt | 1 day ago |
AMAZON-02 - Amazon.com, Inc. (AS16509) | Active | ift.tt | 1 day ago |
AMAZON-02 - Amazon.com, Inc. (AS16509) | Active | ift.tt | 1 day ago |
AMAZON-02 - Amazon.com, Inc. (AS16509) | Active | ift.tt | 1 day ago |
3.167.163.103
AMAZON-02 - Amazon.com, Inc. (AS16509)
Legacy
ift.tt
Seen 1 day ago
3.167.163.127
AMAZON-02 - Amazon.com, Inc. (AS16509)
Legacy
ift.tt
Seen 1 day ago
3.167.163.34
AMAZON-02 - Amazon.com, Inc. (AS16509)
Legacy
ift.tt
Seen 1 day ago
3.167.163.80
AMAZON-02 - Amazon.com, Inc. (AS16509)
Legacy
ift.tt
Seen 1 day ago
18.238.176.129
AMAZON-02 - Amazon.com, Inc. (AS16509)
Active
ift.tt
Seen 1 day ago
18.238.176.86
AMAZON-02 - Amazon.com, Inc. (AS16509)
Active
ift.tt
Seen 1 day ago
18.238.176.47
AMAZON-02 - Amazon.com, Inc. (AS16509)
Active
ift.tt
Seen 1 day ago
18.238.176.71
AMAZON-02 - Amazon.com, Inc. (AS16509)
Active
ift.tt
Seen 1 day ago
Something wrong?