Cloudflare Radar
Scan report
Open reportdocsend.us mimics the Nimbus Docs platform layout, encouraging users to interact with its login and document sharing features. Because MetaMask and SEAL flag the domain, visitors should avoid submitting any credentials or sensitive information.
Page title: “Nimbus Docs — Secure document sharing for teams”
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.
URLScan capture · 2026-11-22 11:18 UTC · SHA-256 9046f9af…f5606cf
PhishDestroy analysis, reviewed version
The page opens with a clean layout bearing the heading "Nimbus Docs" in the top left corner, accompanied by navigation links for "Product", "Security", "Pricing", and "Sign in". The main headline reads "Share sensitive documents without losing control", followed by explanatory text stating that "Nimbus Docs gives your team secure links with view tracking, watermarking and instant access revoke — so confidential files stay confidential." Below this text, two prominent action buttons say "Get started" and "See how it works". Further down, three feature boxes detail "Access controls", "View analytics", and "Secure viewer" with explanatory blurbs about permissions, device tracking, and desktop viewer restrictions. The footer displays a copyright notice for "© 2026 Nimbus Labs Inc." alongside links for "Privacy", "Terms", and "Status".
It was registered on 21 Nov 2026 and reported the same day. MetaMask and SEAL block it, so security products recognize the risk associated with this login setup. Furthermore, it sits behind Cloudflare, which hides the real server, helping mask the destination server behind a commercial proxy.
Pages mimicking services like Nimbus Docs usually aim to capture user accounts or enterprise login details when visitors click sign-in prompts. Entering credentials on such a page hands your password directly to unknown operators, risking unauthorized access to your actual accounts. Because MetaMask and SEAL block it, you should avoid interacting with the forms entirely.
Scan report
Open reportPage capture
SHA-256 a601ead4…c0b7a35
Separate stored monitor snapshot; does not replace the primary report record or establish current availability.
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-11-22T11:24:32Z; First: 2026-11-22T11:24:32Z; Changes: 0; Days archived: 1; Avg page bytes: 2842 |
| Crawler rules | Agents: *; Present: ✓; Disallow: / |
| Page title and metadata | Title: Nimbus Docs — Secure document sharing for teams; Description: Nimbus Docs helps teams share sensitive documents securely with access controls, view tracking and expiring links. |
| Trackers | Requests: 1 |
| Forms and mixed content | Third party scripts: 0 |
| Status | Up: ✓; Code: 200; Timings: DNS: 0; Wait: 71; Download: 1; Response ms: 193 |
| 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 |
| Carbon | Bytes: 3424; Co2 grams: 0.0001; Cleaner than: 95 |
| DNS server | NS: (IP: 162.159.44.175; Host: anton.ns.cloudflare.com), (IP: 162.159.38.219; Host: clara.ns.cloudflare.com); Zone: docsend.us |
| Quality | Cls: 0; Seo: 54; Si s: 0.79; Fcp s: 0.79; Lcp s: 0.79; Tbt ms: 0; Performance: 100; Accessibility: 81; Best practices: 100 |
| Location | IP: 2606:4700:3030::ac43:dce1; ASN: 13335; Org: Cloudflare, Inc.; City: San Francisco; Country: US |
| SSL | San: *.docsend.us, docsend.us; Bits: 256; Chain: docsend.us, YE2, Root YE, ISRG Root X2, ISRG Root X1; Issuer: Let's Encrypt / YE2; Serial: 06D4EB252547913208CE1246F9414ED11E97; SHA256: 4d6d2d5ed1308387df6f0f6c0e0ba0aadc09926525ab4ff30c7e6d46cb352f60; Subject: docsend.us; Valid to: 2027-02-19T11:48:34Z; Valid from: 2026-11-21T11:48:35Z |
| DNS records | A: 104.21.24.224, 172.67.220.225; NS: clara.ns.cloudflare.com, anton.ns.cloudflare.com; Soa: Nsname: anton.ns.cloudflare.com; Hostmaster: dns.cloudflare.com; Serial: 2420751129; Refresh: 10000; Retry: 2400; Expire: 604800; Minttl: 1800; Aaaa: 2606:4700:3035::6815:18e0, 2606:4700:3030::ac43:dce1 |
| Dnssec | Ds: ✗; Rrsig: ✗; Dnskey: ✗ |
| Hsts | Message: Site does not serve any HSTS headers. |
| HTTP security policies | Xframeoptions: ✗; Referrerpolicy: ✗; Xxssprotection: ✗; Permissionspolicy: ✗; Xcontenttypeoptions: ✗; Contentsecuritypolicy: ✗; Stricttransportpolicy: ✗; Crossoriginopenerpolicy: ✗; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗ |
| Firewall | Waf: Cloudflare; Has waf: ✓ |
| Get IP | IP: 2606:4700:3030::ac43:dce1; Family: 6 |
| Redirects | Chain: https://docsend.us |
| Subdomains | Count: 1; Subdomains: www.docsend.us |
| Tech stack | Technologies: Cloudflare, HTTP/3 |
| Page links | Internal: https://docsend.us/; Internal count: 1 |
| Registration record | Registrar: NICENIC INTERNATIONAL GROUP CO., LIMITED; Registrar iana ID: 3765; Registrar URL: https://nicenic.com; Created: 2026-11-21T12:28:18Z; Updated: 2026-11-21T12:30:00Z; Expires: 2027-11-21T12:28:18Z; Status: clientTransferProhibited https://icann.org/epp, clientDeleteProhibited https://icann.org/epp, serverTransferProhibited https://icann.org/epp, addPeriod https://icann.org/epp; Nameservers: clara.ns.cloudflare.com, anton.ns.cloudflare.com; Dnssec: unsigned |
| HTTP headers | Headers: Server: cloudflare; Content type: text/html; charset=utf-8 |
No, this page uses the Nimbus Docs name and branding to present itself as the official site. Real document sharing services operate under verified corporate addresses rather than newly created domains like docsend.us.
Entering credentials on docsend.us hands your login details directly to operators behind the clone. If you typed a password here, change it immediately on any other service where you reuse that combination.
It was registered on 21 Nov 2026 and reported the same day. MetaMask and SEAL block it.
Last checked
Edge-IP reputation is not attributed to this domain.
anton.ns.cloudflare.comclara.ns.cloudflare.comnsname: anton.ns.cloudflare.comhostmaster: dns.cloudflare.comserial: 2420751129refresh: 10000retry: 2400expire: 604800minttl: 1800Location describes the IP network.
4d6d2d5ed1308387df6f0f6c0e0ba0aadc09926525ab4ff30c7e6d46cb352f60*.docsend.usdocsend.usSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.docsend.usDomain recordGoogle PageSpeed Insights — mobile performance audit of docsend.us ·
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://docsend.us/https://docsend.us/Content-Type: text/html; charset=utf-8Server: cloudflareCache-Control: public, max-age=3600CF-Cache-Status: DYNAMICContent-Encoding: gziph3=":443"; ma=86400public, max-age=3600DYNAMICa5e78b13a8662853-ARNkeep-alivegziptext/html; charset=utf-8Sun, 22 Nov 2026 11:20:09 GMTSat, 21 Nov 2026 15:03:55 GMT{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=o6W7UOO2QN8FN7uTSUX40HOyQ1KlZnt1%2FQ416kez%2BNktzvkpIrcXSCA7bQOeB6luuGx0NPXGDmWvNoPEMG0%2FrexrSVsKADUc4EpGv9at%2BbiZ%2BxPGmmUWhc81nfkS"}]}cloudflarecfCacheStatus;desc="DYNAMIC"chunkedaccept-encodingnoindex, nofollowValues 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: 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-11-22 11:23 UTC.
Open this scan on URLScan 01a202fa-a4b3-763b-ad4b-c822e6a29ddd ↗
Loads saved data; the suspicious site is not opened.
| # | Network request | HTTP method · status | Type | Uncompressed size | Response body SHA-256 |
|---|
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Reachable
Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.
Recorded events: 10. 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.
docsend.us 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 ↗
docsend.us)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.