URLQuery
3 det.
Open reportPhishDestroy first recorded com-authorization-v3.digital on 2026-06-11. Listed by external blocklists: MetaMask, SEAL.
Page title: “com-authorization-v3.digital | 521: Web server is down”
Listed by external blocklists: MetaMask, SEAL. 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 capture of com-authorization-v3.digital, taken on 2026-06-25, shows a blank page: the HTML title reads "com-authorization-v3.digital | 521: Web server is down", indicating the origin web server was unreachable when the screenshot was taken. No page content, branding, or interactive elements were visible, so the captured purpose is limited to this server-error response.
VirusTotal results for this domain record 9 flagged detections out of 89 engines. Named vendors issuing verdicts include Kaspersky and Fortinet. The scan scope was not preserved in the record, so these results cannot be attributed to a specific scan type.
3 det.
Open reportphishing domain
15 community references
Open reportScan report
Open reportPage capture
Open reportSeparate stored monitor snapshot; does not replace the primary report record or establish current availability.
95 / 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 | Spf lookups: 0 |
|---|---|
| Protective DNS results | Resolvers: 12; Blocked count: 0 |
| Web archive observations | Last: 2026-07-04T02:33:30Z; First: 2026-07-04T02:33:30Z; Changes: 0; Days archived: 1; Avg page bytes: 839 |
| Crawler rules | Agents: *, Amazonbot, Applebot-Extended, Bytespider, CCBot; Present: ✓ |
| TLS connection | Alpn: h2; Cipher: TLS_AES_256_GCM_SHA384; Protocol: TLSv1.3; Versions: TLSv1, TLSv1.1, TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓ |
| Ports | Open: 80, 443, 8080 |
| DNS server | NS: (IP: 108.162.193.246; Host: wesley.ns.cloudflare.com), (IP: 108.162.192.199; Host: melissa.ns.cloudflare.com); Zone: com-authorization-v3.digital |
| Location | IP: 2606:4700:3031::ac43:9afb; ASN: 13335; Org: Cloudflare, Inc.; City: Toronto; Country: CA |
| SSL | Issuer: Google Trust Services / WE1; Subject: com-authorization-v3.digital |
| DNS records | A: 104.21.72.208, 172.67.154.251; NS: melissa.ns.cloudflare.com, wesley.ns.cloudflare.com; Soa: Nsname: melissa.ns.cloudflare.com; Hostmaster: dns.cloudflare.com; Serial: 2416325067; Refresh: 10000; Retry: 2400; Expire: 604800; Minttl: 1800; Aaaa: 2606:4700:3031::6815:48d0, 2606:4700:3031::ac43:9afb |
| Dnssec | Ds: ✗; Rrsig: ✗; Dnskey: ✗ |
| Hsts | Message: Site does not serve any HSTS headers. |
| HTTP security policies | Xframeoptions: SAMEORIGIN; Referrerpolicy: same-origin; Xxssprotection: ✗; Permissionspolicy: ✗; Xcontenttypeoptions: ✗; Contentsecuritypolicy: ✗; Stricttransportpolicy: ✗; Crossoriginopenerpolicy: ✗; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗ |
| Firewall | Waf: Cloudflare; Has waf: ✓ |
| Get IP | IP: 2606:4700:3031::ac43:9afb; Family: 6 |
| Tech stack | Technologies: Cloudflare, HTTP/3 |
| HTTP headers | Headers: Server: cloudflare; Content type: text/html; charset=UTF-8; X frame options: SAMEORIGIN; Referrer policy: same-origin |
PhishDestroy rates com-authorization-v3.digital as critical risk (evidence score 100/100) from the recorded evidence; it was first recorded on 2026-06-11. Listed by external blocklists: MetaMask, SEAL. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.
Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on com-authorization-v3.digital. A confirmed blockchain transaction cannot be reversed.
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.
Last checked
1cae085cf93c8f2c0a9bcbdc4fb84f92692e12202dacadd0a4559d56fa248bca · 6109 bytes 347e7f511948dc79374461857a9790f75cd4793224168f7d4e89ddd1cc4a5226 · 1977 bytes 347e7f511948dc79374461857a9790f75cd4793224168f7d4e89ddd1cc4a5226 · 1977 bytes 5b685b6fd0c356b8389e33596a40c60d2f63ca6aac5f9ec6250f109105361924 · 8588 bytes 
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Edge-IP reputation is not attributed to this domain.
melissa.ns.cloudflare.comwesley.ns.cloudflare.comnsname: melissa.ns.cloudflare.comhostmaster: dns.cloudflare.comserial: 2416325067refresh: 10000retry: 2400expire: 604800minttl: 1800Location describes the IP network.
b386b39b97bf5a709f154d7eb211261fc5914b68e0c55828fe14b25b73aaa90bcom-authorization-v3.digital*.com-authorization-v3.digitalSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
The site was redirecting visitors elsewhere at the latest check.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Network requests: 2 SHA-256 hashes: 2 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 04:01 UTC.
Open this scan on URLScan 019eb549-ead3-763b-9915-5e9e9b0562cb ↗
Loads saved data; the suspicious site is not opened.
| # | Network request | HTTP method · status | Type | Uncompressed size | Response body SHA-256 |
|---|
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
Our scanner could not complete this check.
com-authorization-v3.digital Source: domain_monitor. This stored snapshot does not establish current availability.
Recorded events: 14. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Lifecycle
Reported 6 d 14 h after registration
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 |
|---|
Reported by 1 community member, first seen 2026-06-11
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 ↗
com-authorization-v3.digital)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.