VirusTotal
11 / 91
The domain teams-login.com returned an HTTP 403 status code on 2026-10-01, indicating a restricted or denied access attempt on that date. Additionally, the domain was previously observed in the PhishDestroy internal listing, highlighting its monitoring status within that catalogue.
On 2026-10-01, a recorded HTTP check showed a 403 response from teams-login.com. The domain was listed in the PhishDestroy internal catalogue as of the latest evidence. VirusTotal checked the domain on 2026-10-01, reporting 11 detections out of 91 scanners. OTX referenced teams-login.com in four pulses as of 2026-09-23. The registrar is Key-Systems GmbH, and the SSL certificate was issued by Let's Encrypt / YR1, as scanned on 2026-09-21.
These observations from HTTP, VirusTotal, OTX, and the PhishDestroy catalogue provide a multi-faceted view of teams-login.com’s recent status. The HTTP 403 code documents a specific access result, while the presence in PhishDestroy and OTX pulses indicates ongoing monitoring across multiple platforms. VirusTotal’s findings reflect how the domain was evaluated by a range of security scanners at a distinct point in time.
Review teams-login.com’s status in the PhishDestroy catalogue and compare it with the OTX pulse references for a broader context. Preserve the dated HTTP response and VirusTotal scan records for future comparison and to track any changes in subsequent evaluations.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
nginxScanner note: alive_content: raw=short_403; http=403; via=https_proxy; server=nginx
ns2.transip.eumx.security-learning.nlpriority 10Location describes the IP network.
f5cb4c51ae46307b0cc4e21eb079488bce03195178b2fee2e48d226f1eebb21aSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of teams-login.com · checked Sep 23, 2026
7 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive