Cloudflare Radar
Scan report
Open reportww1.toastlogin.com: VirusTotal 0/92 detections. First recorded 2026-10-25. Registrar: Media Elite Holdings Limited.
Use caution — do not enter credentials or personal information.
Risk score, higher = worse · How this score works
Pick what happened and tick the steps as you go. The ticks are kept only in this browser.
Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.
PhishDestroy analysis, earlier unreviewed version
The captured screenshot shows a dark landing page with a login-themed header, a Related Searches label, and five large buttons reading EMPLOYEE PAYROLL, ONLINE ACCOUNT LOGIN, SECURE ONLINE LOGIN SOLUTIONS, SECURE PASSWORD MANAGER and PASSWORD MANAGEMENT FOR WEBSITES, above a privacy policy link. PhishDestroy listed the domain as credential phishing from a trusted report, first seen on 2026-10-25.
The five tiles trade on payroll and account-login intent, steering a visitor toward an account-access flow on a look-alike host instead of a genuine service page. As a category risk, such lures harvest usernames, passwords and other login secrets when a visitor types them into an impersonated sign-in path.
Screenshot: the page presented related-search tiles promising payroll and secure login or password-management options rather than a real product interface. urlscan captured it on 2026-09-01 with a malicious verdict of false and an engine ML score of -40, recording a redirect funnel that moved from the parent domain into ww1.toastlogin.com via a 302 and then cycled 307 between HTTP and HTTPS. VirusTotal did not flag it, Google Safe Browsing was not flagged on 2026-10-26, Spamhaus was not listed on 2026-10-25, OTX recorded 0 pulses on 2026-10-25, and external blocklists counted 0 on 2026-10-26 while the PhishDestroy internal blocklist matched. Site inspection recorded a consent-management script layer, Microsoft Clarity analytics and a Microsoft advertising script across 20 requests with 1 tracker.
Notable weaknesses: DNSSEC is unsigned, only SPF is published with no DKIM or DMARC, and no CAA records were recorded. The connection used TLS 1.3 with AES-256-GCM, forward secrecy, ALPN http/1.1 and an authorized certificate. Hosting is recorded at Confluence Networks Inc on ASN 40034, returning a Cowboy server banner.
If you submitted credentials, change your password on the genuine service, enable two-factor authentication, and review recent sign-in activity for unexpected access. Treat any message leading here as phishing and do not reuse the submitted password. Defenders should block ww1.toastlogin.com at DNS or proxy level and watch for the parent-domain redirect path feeding it.
Scan report
Open reportPage capture
SHA-256 e34f2036…741277a
Separate stored monitor snapshot; does not replace the primary report record or establish current availability.
15 / 100 · heuristic score · 0 brand references · 1 classification
Content heuristic only; not the final score
Open reportThis dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.
Narrative generation metadata
Open reportThe narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.
Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
Stored page, network and scanner observations, grouped by source and observation time.
| Mail configuration | MX: ~; Spf: v=spf1 a -all; Spf lookups: 1 |
|---|---|
| Caa records | Domain: ww1.toastlogin.com |
| Protective DNS results | Resolvers: 12; Blocked count: 0 |
| Web archive observations | Last: 2026-10-25T15:03:05Z; First: 2025-02-24T11:16:01Z; Changes: 1; Days archived: 2; Scans per day: 0; Avg page bytes: 4457 |
| Trackers | Requests: 1 |
| TLS connection | Alpn: http/1.1; Cipher: TLS_AES_256_GCM_SHA384; Protocol: TLSv1.3; Authorized: ✓; Ocsp stapled: ✓; Forward secrecy: ✓ |
| Ports | Open: 80 |
| DNS server | NS: (IP: 208.115.240.170; Host: ns1.redfoxdns.com), (IP: 77.247.182.241; Host: ns2.redfoxdns.com); Zone: toastlogin.com |
| Location | IP: 208.91.196.145; ASN: 40034; Org: Confluence Networks Inc; City: Road Town; Country: VG |
| SSL | Issuer: ZeroSSL GmbH / ZeroSSL ECC DV SSL CA 2; Subject: ww1.toastlogin.com |
| DNS records | A: 208.91.196.145; MX: Exchange: ~; Priority: 300; NS: ns1.cnomy.com, ns2.cnomy.com; Ptr: ns1.cnomy.com; Soa: Nsname: ns1.cnomy.com; Hostmaster: abuse.confluence-networks.com; Serial: 2011062801; Refresh: 3600; Retry: 900; Expire: 604800; Minttl: 86400; Txt: v=spf1 a -all; Cname: 9145.searchmagnified.com |
| Dnssec | Ds: ✗; Rrsig: ✗; Dnskey: ✓ |
| Get IP | IP: 208.91.196.145; Family: 4 |
| Subdomains | Count: 2; Subdomains: ww1.toastlogin.com, www.toastlogin.com |
| Page links | Internal count: 1 |
| Registration record | Registrar: Media Elite Holdings Limited, S.A.; Created: 2019-08-26T20:22:56Z; Updated: 2026-08-01T02:04:03Z; Expires: 2027-08-26T20:22:56Z; Status: clientTransferProhibited https://icann.org/epp; Nameservers: ns1.redfoxdns.com, ns2.redfoxdns.com |
ns1.redfoxdns.comns2.redfoxdns.comnsname: ns1.cnomy.comhostmaster: abuse.confluence-networks.comserial: 2011062801refresh: 3600retry: 900expire: 604800minttl: 86400~priority 300Location describes the IP network.
*.toastlogin.comtoastlogin.comSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
The site was serving its pages at the latest check.
Google PageSpeed Insights — mobile performance audit of ww1.toastlogin.com ·
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://ww1.toastlogin.com/Server: nginx/1.28.0Content-Type: text/htmlContent-Encoding: gzip4236a047946cb67d6a7e839ec4fee7092e36705e2ebb69f80a5614aa3adf8eeekeep-alivegziptext/htmlSun, 25 Oct 2026 15:04:01 GMTnginx/1.28.0chunked1.1 google21-ynpfValues retained by the collector; long values may be shortened during collection.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Network requests: 20 SHA-256 hashes: 20 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-10-29 01:57 UTC.
Open this scan on URLScan 01a05cc5-e551-73fd-902d-dde5d3231afd ↗
Loads saved data; the suspicious site is not opened.
| # | Network request | HTTP method · status | Type | Uncompressed size | Response body SHA-256 |
|---|
Recorded events: 7. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Lifecycle
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.
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| ID | Stored data |
|---|
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
ww1.toastlogin.com 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.
The draft stays only with you.
First secure your money: call your bank or revoke wallet approvals. Immediate steps →
Emergency help from security researchers when a crypto wallet is being drained right now.
Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.
Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.
Forward scam emails and text messages to the National Cyber Security Centre, which takes down the malicious sites it finds.
Emailreport@phishing.gov.uk Text messages7726Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.
Forward phishing emails to the Anti-Phishing Working Group.
Emailreportphishing@apwg.orgNational Cyber Crime Reporting Portal. For financial fraud, also call the 1930 helpline straight away.
Helpline1930Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
ww1.toastlogin.com)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
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
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.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
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.