Skip to security report
login-c.net favicon
Domain security and threat intelligence

login-c.net

I was scammed — help me write a report
Share / download report
Post on X Send in Telegram Check via API
In short

PhishDestroy first recorded login-c.net on 2026-11-11. Stored VirusTotal result: 5/92 engines flagged. Malicious: 2. Suspicious: 3. Analysis time (as stored): 2026-11-07 10:00 UTC. Retrieved (as stored): 2026-11-11 08:25 UTC.

Page title: “Outlook”

More about the sources
Recorded security signals

Stored VirusTotal result: 5/92 engines flagged. Malicious: 2. Suspicious: 3. Analysis time (as stored): 2026-11-07 10:00 UTC. Retrieved (as stored): 2026-11-11 08:25 UTC. Use caution — do not enter credentials or personal information.

VirusTotal detections: 5/92
Registrar
Wild West Domains
Resolved IP
Bulgaria101.99.94.126Shinjiru Technology Sdn Bhd · CDN
Registered
2026-08-20
First seen by PhishDestroy
2026-11-11
OTX
community references
Page captures
open gallery
OTX: 3 refs 2026-11-11 CDN

Risk score, higher = worse · How this score works

What to do right now

Pick what happened and tick the steps as you go. The ticks are kept only in this browser.

Entered a password0/3
Paid or entered card or bank details0/2
Downloaded a file0/2
Shared a seed phrase or private key0/3
Approved token spending (approve / permit)0/3
Connected a wallet but signed nothing0/2
Sent crypto0/3
Write a police report

Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.

Analysis

Domain summary

PhishDestroy first recorded login-c.net on 2026-11-11. Stored VirusTotal result: 5/92 engines flagged. Malicious: 2. Suspicious: 3. Analysis time (as stored): 2026-11-07 10:00 UTC. Retrieved (as stored): 2026-11-11 08:25 UTC. Risk: critical (evidence score 100/100). Registrar: Wild West Domains. Status: Last known active. Hosting: Shinjiru Technology Sdn Bhd. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
5 / 92
Hosting
Bulgaria101.99.94.126Shinjiru Technology Sdn Bhd · CDN
Registrar
Wild West Domains
Registered
2026-08-20
OTX
3 community refs
Page captures
5

Recorded source summary

PhishDestroy first observed login-c.net on Nov 11, 2026. Stored content metadata identifies Microsoft as the apparent target. The captured page title is “Outlook”. Current evidence score: 100/100 (critical).

One source contains a positive finding: VirusTotal. VirusTotal recorded 5 detections among 92 engines: DNS8, VIPRE, SOCRadar, Gridinsoft, alphaMountain.ai on Nov 7, 2026 at 10:00 UTC. Additional recorded evidence: AlienVault OTX listed 3 community pulse references (not vendor detections) on Nov 14, 2026 at 05:16 UTC.

HTTP 302 was recorded on Nov 22, 2026 at 11:17 UTC. Latest classified outcome: redirect observed; cause http redirect on Nov 22, 2026 at 10:17 UTC. Registration records for the domain list Wild West Domains, LLC as the registrar and Jul 9, 2002 as the creation date. At collection time, the hostname resolved to 101.99.94.126 on AS45839 (Shinjiru Technology Sdn Bhd). The IP and ASN identify shared Vercel edge infrastructure; the origin server is not established by this address. The stored server header is Apache. DOM analysis on Nov 11, 2026 at 15:20 UTC returned 15/100. The evidence archive retains 5 visual captures from URLScan and Cloudflare Radar. TLS metadata lists YR1 as the certificate issuer with validity through Dec 19, 2026.

Stored content provides classification context alongside the positive source finding. The target field identifies Microsoft.

Source evidenceVirusTotal 5 / 92 · OTX 3 references 5 sources

VirusTotal

5 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 14 fields
Separate collector summary

This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.

Source
VirusTotal
Result state
observed
Numerator
16
Denominator
92
Vendors
alphaMountain.ai, BitDefender, CRDF, DNS8, ESET, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft, Kaspersky, Lionic, Seclookup, SOCRadar, Sophos, VIPRE, Webroot
Checked at
2026-11-16 04:07:24
Fetched at
2026-11-16 03:07:24

OTX

3 community references

Open report

URLScan

Page capture

SHA-256 f3d272e4…0e73c16

Open report
URLScanOriginal source recordObserved: 22 fields
Separate monitor record · 2026-11-12 04:30 UTC

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

UUID
01a141a8-1e10-7014-b4d3-7fba77fcc72c
Score
0
Malicious
✗
Result at
2026-11-12T04:30:23Z
Enriched at
2026-11-11T09:12:14Z
Source timestamps
Urlscan result at: 2026-11-12 05:30:23; Urlscan enriched at: 2026-11-11 10:12:14

PhishDestroy DOM

15 / 100 · heuristic score · 0 brand references · 0 classifications

Content heuristic only; not the final score

Open report
Page code check by a separate monitor · 15 / 100 · 2026-11-11 15:20 UTC

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

Heuristic score
15
Analyzed at
2026-11-11T15:20:09Z
Source timestamp
2026-11-11 16:20:09

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 23 fields

Mail configuration

MX records
  • loginc-net01c.mail.protection.outlook.com
SPF record
v=spf1 include:spf.protection.outlook.com -all
Providers
  • Microsoft 365
SPF lookups
1

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Page title and metadata

Page title
Outlook
Indexing directives
{{RobotNoIndex}}

Trackers

Requests
1

Forms and mixed content

Upgrades insecure requests
Yes
Third-party scripts
2

HTTP response

Reachable
Yes
HTTP status
302
Request timings, ms
DNS
28
TLS
80
Waiting
31
Connection
38
Download
0
Response time, ms
177

TLS connection

ALPN
h2
Cipher
TLS_CHACHA20_POLY1305_SHA256
Protocol
TLSv1.3
Supported versions
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 80
  • 443

Carbon estimate

Bytes
14282
CO₂, grams
0.0005
Cleaner than, %
64

DNS servers

Nameservers
  • IP address
    150.171.21.208
    Host
    ns2.bdm.microsoftonline.com
  • IP address
    204.14.183.208
    Host
    ns3.bdm.microsoftonline.com
  • IP address
    208.84.5.208
    Host
    ns4.bdm.microsoftonline.com
  • IP address
    13.107.236.208
    Host
    ns1.bdm.microsoftonline.com
DNS zone
login-c.net

Cookies

Cookies
  • Name
    ClientId
    Secure
    Yes
    SameSite
    None
  • Name
    ClientId
    Secure
    Yes
    SameSite
    None

Location

IP address
101.99.94.126
ASN
45839
Organization
Shinjiru Technology Sdn Bhd
City
Sofia
Country
BG

TLS certificate

Issuer
Let's Encrypt / YE2
Subject
login-c.net

DNS records

A
  • 101.99.94.126
MX
  • Mail server
    loginc-net01c.mail.protection.outlook.com
    Priority
    0
NS
  • ns2.bdm.microsoftonline.com
  • ns4.bdm.microsoftonline.com
  • ns1.bdm.microsoftonline.com
  • ns3.bdm.microsoftonline.com
SOA
Primary nameserver
ns1.bdm.microsoftonline.com
Hostmaster
azuredns-hostmaster.microsoft.com
Serial
1
Refresh, seconds
3600
Retry, seconds
300
Expiry, seconds
2419200
Minimum TTL, seconds
300
TXT
  • mscid=q9UbGPUNaQ5mK+dizkyaqcxEEVxHYvGF31ACOFlibZxB9JP1TFG2gH3gRvM4gkeakTxkoei1gpn09C+mXI+23Q==
  • v=spf1 include:spf.protection.outlook.com -all

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Header value
max-age=31536000; includeSubDomains
Observation
HSTS header does not contain the preload directive.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
no-referrer
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
nosniff
Content-Security-Policy
default-src *.res.office365.com *.fluidpreview.office.net *.cdn.office.net *.df.onecdn.static.microsoft *.public.onecdn.
Strict-Transport-Security
max-age=31536000; includeSubDomains
Cross-Origin-Opener-Policy
same-origin-allow-popups
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
101.99.94.126
IP version
4

Redirects

Redirect chain
  • https://login-c.net
  • https://outlook.office.com
  • https://outlook.office.com/mail/
  • https://outlook.cloud.microsoft/mail/
Count
3

Subdomains

Count
2
Subdomains
  • go.login-c.net
  • www.login-c.net

Technology stack

Technologies
  • Microsoft HTTPAPI
  • MobX
  • HSTS
  • Webpack
  • Module Federation
  • HTTP/3

Registration record

Registrar
Wild West Domains, LLC
Registered
Updated
Expires
Status
  • clientDeleteProhibited https://icann.org/epp
  • clientRenewProhibited https://icann.org/epp
  • clientTransferProhibited https://icann.org/epp
  • clientUpdateProhibited https://icann.org/epp
Nameservers
  • ns1.bdm.microsoftonline.com
  • ns2.bdm.microsoftonline.com

HTTP headers

Response headers
Server
Microsoft-HTTPAPI/2.0
Content-Type
text/html
Strict-Transport-Security
max-age=31536000; includeSubDomains
Content-Security-Policy
default-src *.res.office365.com *.fluidpreview.office.net *.cdn.office.net *.df.onecdn.static.microsoft *.public.onecdn.static.microsoft swx.cdn.skype.com 'self'; script-src 'nonce-pbeqrvDuzbp3RpenZ07SjQ==' *.res.office365.com *.fluidpreview.office.net shellprod.msocdn.com amcdn.msauth.net amcdn.msf
X-Content-Type-Options
nosniff
Referrer-Policy
no-referrer
Cross-Origin-Opener-Policy
same-origin-allow-popups
Link
<https://res.public.onecdn.static.microsoft/>; rel="preconnect"
Original source fields · JSON
Mail configuration
MX: loginc-net01c.mail.protection.outlook.com; Spf: v=spf1 include:spf.protection.outlook.com -all; Providers: Microsoft 365; Spf lookups: 1
Protective DNS results
Resolvers: 12; Blocked by: CloudFlare Family; Blocked count: 1
Page title and metadata
Title: Outlook; Robots: {{RobotNoIndex}}
Trackers
Requests: 1
Forms and mixed content
Upgrade insecure: ✓; Third party scripts: 2
Status
Up: ✓; Code: 302; Timings: DNS: 28; TLS: 80; Wait: 31; Connect: 38; Download: 0; Response ms: 177
TLS connection
Alpn: h2; Cipher: TLS_CHACHA20_POLY1305_SHA256; Protocol: TLSv1.3; Versions: TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓
Ports
Open: 80, 443
Carbon
Bytes: 14282; Co2 grams: 0.0005; Cleaner than: 64
DNS server
NS: (IP: 150.171.21.208; Host: ns2.bdm.microsoftonline.com), (IP: 204.14.183.208; Host: ns3.bdm.microsoftonline.com), (IP: 208.84.5.208; Host: ns4.bdm.microsoftonline.com), (IP: 13.107.236.208; Host: ns1.bdm.microsoftonline.com); Zone: login-c.net
Cookies
Cookies: (Name: ClientId; Secure: ✓), (Name: ClientId; Secure: ✓)
Location
IP: 101.99.94.126; ASN: 45839; Org: Shinjiru Technology Sdn Bhd; City: Sofia; Country: BG
SSL
Issuer: Let's Encrypt / YE2; Subject: login-c.net
DNS records
A: 101.99.94.126; MX: Exchange: loginc-net01c.mail.protection.outlook.com; Priority: 0; NS: ns2.bdm.microsoftonline.com, ns4.bdm.microsoftonline.com, ns1.bdm.microsoftonline.com, ns3.bdm.microsoftonline.com; Soa: Nsname: ns1.bdm.microsoftonline.com; Hostmaster: azuredns-hostmaster.microsoft.com; Serial: 1; Refresh: 3600; Retry: 300; Expire: 2419200; Minttl: 300; Txt: mscid=q9UbGPUNaQ5mK+dizkyaqcxEEVxHYvGF31ACOFlibZxB9JP1TFG2gH3gRvM4gkeakTxkoei1gpn09C+mXI+23Q==, v=spf1 include:spf.protection.outlook.com -all
Dnssec
Ds: ✗; Rrsig: ✗; Dnskey: ✗
Hsts
Header: max-age=31536000; includeSubDomains; Message: HSTS header does not contain the preload directive.
HTTP security policies
Xframeoptions: ✗; Referrerpolicy: no-referrer; Xxssprotection: ✗; Permissionspolicy: ✗; Xcontenttypeoptions: nosniff; Contentsecuritypolicy: default-src *.res.office365.com *.fluidpreview.office.net *.cdn.office.net *.df.onecdn.static.microsoft *.public.onecdn.; Stricttransportpolicy: max-age=31536000; includeSubDomains; Crossoriginopenerpolicy: same-origin-allow-popups; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗
Get IP
IP: 101.99.94.126; Family: 4
Redirects
Chain: https://login-c.net, https://outlook.office.com, https://outlook.office.com/mail/, https://outlook.cloud.microsoft/mail/; Count: 3
Subdomains
Count: 2; Subdomains: go.login-c.net, www.login-c.net
Tech stack
Technologies: Microsoft HTTPAPI, MobX, HSTS, Webpack, Module Federation, HTTP/3
Registration record
Registrar: Wild West Domains, LLC; Created: 2026-08-20T15:26:14Z; Updated: 2026-08-20T15:26:14Z; Expires: 2027-08-20T15:26:14Z; Status: clientDeleteProhibited https://icann.org/epp, clientRenewProhibited https://icann.org/epp, clientTransferProhibited https://icann.org/epp, clientUpdateProhibited https://icann.org/epp; Nameservers: ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com
HTTP headers
Headers: Server: Microsoft-HTTPAPI/2.0; Content type: text/html; Strict transport security: max-age=31536000; includeSubDomains; Content security policy: default-src *.res.office365.com *.fluidpreview.office.net *.cdn.office.net *.df.onecdn.static.microsoft *.public.onecdn.static.microsoft swx.cdn.skype.com 'self'; script-src 'nonce-pbeqrvDuzbp3RpenZ07SjQ==' *.res.office365.com *.fluidpreview.office.net shellprod.msocdn.com amcdn.msauth.net amcdn.msf; X content type options: nosniff; Referrer policy: no-referrer; Cross origin opener policy: same-origin-allow-popups; Link: <https://res.public.onecdn.static.microsoft/>; rel="preconnect"

Questions about login-c.net

Is login-c.net legit?

PhishDestroy rates login-c.net as critical risk (evidence score 100/100) from the recorded evidence; it was first recorded on 2026-11-11. Stored VirusTotal result: 5/92 engines flagged. Malicious: 2. Suspicious: 3. Analysis time (as stored): 2026-11-07 10:00 UTC. Retrieved (as stored): 2026-11-11 08:25 UTC. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is login-c.net safe to connect a wallet?

Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on login-c.net. A confirmed blockchain transaction cannot be reversed.

What should I do if I used login-c.net?

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
  • Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
  • Approved token spending (approve / permit) — revoke that approval with a token-approval checker
  • Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
  • Downloaded a file — do not open it and scan the device with security software

Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Page captures (5)

All capture links and hashes (5)

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 95 report ↗
IP Context Bulgaria101.99.94.126 Vercel shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-11activeall-domainsblocklistcontentcryptodomainsdrainerfraudmonthlyphishdestroyphishingscam
Registrar Wild West Domains
RegistrationCreated 2026-08-20 (94d) — Expires 2027-08-20
HTTP Status302 Found (Temporary)
Technical detailsProvenance & timestamps
First Detected2026-11-11
DOM Analysisanalyzed 2026-11-11score 15/100
Submitted URLhttp://www.login-c.net/
Favicon Hash
Observed page title
Outlook
TLS Certificate
Issued by YR1 · stored validity ends in 26 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
Bulgaria101.99.94.126
Network ASN
AS45839
Organization
Shinjiru Technology Sdn Bhd
Observed location
BulgariaSofia, BG
Server header
Apache

Edge-IP reputation is not attributed to this domain.

Nameservers 4

  • ns1-38.azure-dns.com
  • ns2-38.azure-dns.net
  • ns3-38.azure-dns.org
  • ns4-38.azure-dns.info

SOA

  • nsname: ns1.bdm.microsoftonline.com
  • hostmaster: azuredns-hostmaster.microsoft.com
  • serial: 1
  • refresh: 3600
  • retry: 300
  • expire: 2419200
  • minttl: 300

Registrar abuse contact VirusTotal WHOIS

Mail routing 1 MX record

  • loginc-net01c.mail.protection.outlook.com

Location describes the IP network.

TLS certificate

Issuer
YR1
Valid from
2026-09-20 03:53:19
Valid until
2026-12-19 03:53:18
Hostname match
No
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate names · 2 SANs
  • regenrentals.com
  • www.regenrentals.com

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-11-22 11:17 UTC

The site was redirecting visitors elsewhere at the latest check.

Technical details
Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting DNS: Resolved
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-11-22 11:17 UTC
RDAP registration
Observed timeline last reachable: 2026-11-22 11:17 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Recorded subdomains2

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • go.login-c.netDomain record
  • www.login-c.netDomain record
Technologies · 2 identified
Open complete records

VirusTotal Analysis

5 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive result retrieved by PhishDestroy Previous stored snapshot: 5 detections
DNS8
VIPRE
SOCRadar
Gridinsoft
alphaMountain.ai
PageSpeed (mobile): 57

Google PageSpeed Insights — mobile performance audit of login-c.net ·

57
Needs Work
Performance
FCP
6.21 s
First Contentful Paint
LCP
6.21 s
Largest Contentful Paint
CLS
0.092
Cumulative Layout Shift
TBT
154 ms
Total Blocking Time
SI
6.21 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details2

Availability observations

Last reachable observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

All stored data104
Open complete records

Captured network requests

Network requests: 40 SHA-256 hashes: 40 URLScan scan:

Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-11-11 08:13 UTC.

Open this scan on URLScan 01a141a8-1e10-7014-b4d3-7fba77fcc72c ↗

Stored observation history11

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Redirecting elsewhere

    HTTP redirect

  2. Availability monitor · Recorded state

    Redirecting elsewhere

    HTTP redirect

  3. Availability monitor · Recorded state

    Redirecting elsewhere

    HTTP redirect

  4. Availability monitor · Recorded state

    Redirecting elsewhere

    HTTP redirect

  5. Availability monitor · Recorded state

    Redirecting elsewhere

    HTTP redirect

Earlier observations 6
  1. Availability monitor · Recorded state

    Redirecting elsewhere

    HTTP redirect

  2. Availability monitor · Recorded state

    Redirecting elsewhere

    HTTP redirect

  3. Availability monitor · Recorded state

    Redirecting elsewhere

    HTTP redirect

  4. Availability monitor · Recorded state

    Redirecting elsewhere

    HTTP redirect

  5. Availability monitor · Recorded state

    Redirecting elsewhere

    HTTP redirect

  6. Availability monitor · Recorded state

    Redirecting elsewhere

    HTTP redirect

All retained availability observations38
Open complete records

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Monitoring · in progress

Recorded events: 10. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Pre-emptive Discovery & IngestionThreat Ingested recorded
  • Threat Ingested
    login-c.net detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · OTX Community References · Automated brand label: Microsoft · Forensic Evidence Collected · Technical Analysis Recorded recorded
Publication & AvailabilityDestroyList Published · Monitoring Continues ongoing
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.
    ongoing

Recorded activity

4 entries

Lifecycle

  1. Domain registered
  2. VirusTotal analysis with detections+78 d 18 h
  3. Added to PhishDestroy+3 d 22 h
  1. AlienVault OTX

    3 community references

    +69 h 14 min
  2. Added to PhishDestroy

    login-c.net

    +3 d 22 h
  3. VirusTotal

    5/92 engine detections

    +22 d 11 h
  4. URLScan

    Malicious · engine verdict · score 95

How we investigate & report

Public scans, evidence and abuse channels

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.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

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.

All stored records by source

Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.

Download all records as JSON

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

login-c.net

Evidence & External Reports

Deep Analysis

Were You Affected by This Site?

You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Secure your accounts and funds first, then report. If credentials were compromised, report immediately. Do not engage with recovery scammers.

Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.

Where to report

The draft stays only with you.

First secure your money: call your bank or revoke wallet approvals. Immediate steps →

More: international and crypto channels

Official reporting routes

More official reporting routes
SEAL 911 Worldwide

Emergency help from security researchers when a crypto wallet is being drained right now.

FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
  • Downloaded a file — do not open it and scan the device with security software
  • Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
  • Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
  • Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
  • Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including login-c.net)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →
About this reportSources, observation dates and corrections

This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.

A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/login-c.net"
  title="PhishDestroy threat report for login-c.net"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>