Skip to security report
Analytics Dashboard
Domain security and threat intelligence
elab-stilth.surge.sh favicon

elab-stilth.surge.sh

In short

elab-stilth.surge.sh is a credential phishing page detected by PhishDestroy on 2026-10-22. Risk: high (68/100). Registrar: Surge.sh. Status: Last known active. Hosting: DigitalOcean, LLC. Do not enter credentials or connect a wallet.

“Login”

Registrar
Surge.sh
Resolved IP
188.166.132.94
Registered
Jul 25, 2014
PhishDestroy assessment High
Availability Last known active Latest stored reachability observation Observed · HTTP probe
Risk signals
Stored PhishDestroy threat listing Scam type: Credential Phishing
Oct 22, 2026
API
Suspicious Domain — Listed on PhishDestroy
Stored PhishDestroy threat listing. Exercise extreme caution — do not enter credentials or personal information.
Google Safe Browsing
No threat flag
Page captures
7
open gallery
Domain age
4472 days
Source evidence 3 sources

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

URLScan

No malicious flag

Open report

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.

URLScan · 2026-10-22T19:49:22Z

Observed: · Retrieved:

Uuid
01a16529-013b-709b-8ab3-2e97f205c428
Final url
https://elab-stilth.surge.sh/
Status
200
Ip
188.166.132.94
Contacted domains
[
    "api.93-127-130-207.nip.io"
]
Contacted IP addresses
[
    "93.127.130.207",
    "188.166.132.94"
]
Asns
[
    "401479",
    "14061"
]
Countries
[
    "US",
    "NL"
]
Document hash
c99f0c5cc69c1ad2a56ebda65005dc98a8092ade794e147a1183edc5cd2dad9e
Script hashes
[
    "b6b1d3bdba9b0f3643feb01e526fd6f6dbb4db23c130fdb6ae862d1a94ad55ad"
]
Globals
[
    "__reactRouterVersion"
]
Tls
{
    "san": [
        "*.surge.sh",
        "surge.sh"
    ],
    "cipher": "AES_256_GCM",
    "issuer": "Sectigo Public Server Authentication CA DV R36",
    "subject": "*.surge.sh",
    "protocol": "TLS 1.3",
    "valid_to": "2026-12-16T23:59:59Z",
    "valid_from": "2026-06-01T00:00:00Z"
}
Domain age days
30
Apex age days
30
Tls age days
143
Tls valid days
198
Requests
6
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 99,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "Surge",
    "content-type": "text/html; charset=UTF-8"
}
VirusTotal · 2026-10-22T13:34:26Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 47,
    "malicious": 9,
    "suspicious": 1,
    "undetected": 35
}
Vendor labels
{
    "ESET": "suspicious",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Fortinet": "phishing",
    "LevelBlue": "phishing",
    "BitDefender": "phishing",
    "alphaMountain.ai": "malicious"
}
Reputation
0
Categories
{
    "Sophos": "phishing and fraud",
    "alphaMountain.ai": "Information Technology, Malicious (alphaMountain.ai)",
    "Forcepoint ThreatSeeker": "information technology"
}
Registrar
Porkbun LLC
Created
2014-07-25T23:10:53Z
Expires
2032-07-25T23:10:53Z
Updated
2026-09-22T21:00:26Z
First seen
2026-09-21T06:07:56Z
DNS records
[
    {
        "ttl": 3600,
        "type": "A",
        "value": "159.203.50.177"
    }
]
Dns at
2026-10-22T13:35:54Z
Jarm
2ad2ad0002ad2ad00042d42d0000005d86ccb1a0567e012264097a0315d7a7
Certificate
{
    "san": [
        "*.surge.sh",
        "surge.sh"
    ],
    "issuer": "Sectigo Limited / Sectigo Public Server Authentication CA DV R36",
    "serial": "a5542a5e7aea4e5832f44440bfeda08d",
    "sha256": "97b6f955e414ca95a3c57ecae57c2cba8532736157112d6cc11f56a5a790058a",
    "subject": "*.surge.sh",
    "valid_to": "2026-12-16T23:59:59Z",
    "valid_from": "2026-06-01T00:00:00Z"
}
Registration record
{
    "registrar": "Porkbun LLC",
    "registrar_iana_id": "1861",
    "registrar_url": "http://porkbun.com",
    "created": "2014-07-25T23:10:53Z",
    "updated": "2026-09-22T21:00:26Z",
    "expires": "2032-07-25T23:10:53Z",
    "status": [
        "clientDeleteProhibited",
        "clientTransferProhibited"
    ],
    "nameservers": [
        "ns1.surge.world",
        "ns2.surge.world",
        "ns3.surge.world",
        "ns4.surge.world"
    ],
    "dnssec": "unsigned"
}
Website checks · 2026-10-23T18:42:51Z
Caa records
{
    "domain": "elab-stilth.surge.sh"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Crawler rules
{
    "agents": [
        "*"
    ],
    "present": true
}
Page title and metadata
{
    "title": "Login",
    "themeColor": "#000000",
    "description": "Login"
}
Trackers
{
    "requests": 5
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 1326,
        "tls": 16,
        "wait": 17,
        "connect": 15,
        "download": 0
    },
    "response_ms": 1374
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        22,
        53,
        80
    ]
}
Carbon
{
    "bytes": 512,
    "co2_grams": 0,
    "cleaner_than": 95
}
Dns server
{
    "ns": [
        {
            "ip": "165.22.238.141",
            "host": "ns3.surge.world"
        },
        {
            "ip": "159.223.133.160",
            "host": "ns4.surge.world"
        },
        {
            "ip": "165.227.17.224",
            "host": "ns1.surge.world"
        },
        {
            "ip": "209.38.166.73",
            "host": "ns2.surge.world"
        }
    ],
    "zone": "surge.sh"
}
Location
{
    "ip": "188.166.132.94",
    "asn": "14061",
    "org": "DigitalOcean, LLC",
    "city": "Amsterdam",
    "country": "NL"
}
Ssl
{
    "issuer": "Sectigo Limited / Sectigo Public Server Authentication CA DV R36",
    "subject": "*.surge.sh"
}
DNS records
{
    "A": [
        "188.166.132.94"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "188.166.132.94",
    "family": 4
}
Redirects
{
    "chain": [
        "https://elab-stilth.surge.sh"
    ]
}
HTTP headers
{
    "headers": {
        "server": "Surge",
        "content-type": "text/html; charset=UTF-8"
    }
}

Questions about elab-stilth.surge.sh

Is elab-stilth.surge.sh legit?

No. PhishDestroy classifies elab-stilth.surge.sh as a credential phishing page (risk: high, 68/100); it was first detected on 2026-10-22. Treat the site as unsafe.

Is elab-stilth.surge.sh safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on elab-stilth.surge.sh. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used elab-stilth.surge.sh?

Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Stored Capture · 7 captures

Primary capture 1 / 7
SourcePrimary capture
Recorded2026-10-22 19:50 UTC
StateStored capture
Position1 / 7
Open capture Wayback Download

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Reputation abuse score 0/100 0 reports checked Oct 22, 2026
Registrar (base domain) Surge.sh
Abuse contactabuse@surge.sh, abuse@digitalocean.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for surge.sh →
Registration (base domain)surge.sh · Created Jul 25, 2014 — Expires Jul 25, 2032
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 22, 2026
DOM Analysisanalyzed Oct 23, 2026score 68/100
Submitted URLhttps://elab-stilth.surge.sh/
Favicon Hash
Observed page title
Login
TLS Certificate
Issued by Sectigo Public Server Authentication CA DV R36 · stored validity ends in 54 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
188.166.132.94
Network ASN
AS14061
Organization
Digitalocean
Observed location
Amsterdam, NL
Server header
Surge

Location describes the IP network.

TLS certificate

Issuer
Sectigo Public Server Authentication CA DV R36
Valid from
2026-06-01 00:00:00
Valid until
2026-12-16 23:59:59
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint97b6f955e414ca95a3c57ecae57c2cba8532736157112d6cc11f56a5a790058a
Certificate names · 2 SANs
  • *.surge.sh
  • surge.sh

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

viewdns.info · 188.166.132.94rapiddns.io

Latest Classified Outcome 2026-10-23 10:00:38 UTC

Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Stale Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-10-23 10:00:38 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-23 10:00:38 UTC last content: 2026-10-23 10:00:38 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.
Report This Domain Submit evidence & help protect others
Registration & observation details3

Availability observations

Last reachable observation
Last content 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.

Stored observation history2

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

    Unknown→live_content

    content_served

  2. Availability monitor · First collection record

    Reachable

Recorded activity

3 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. Added to PhishDestroy

    elab-stilth.surge.sh

    View source
  3. URLScan

    Page captured

    View source

Check for cloaking

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

elab-stilth.surge.sh

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal ChainPatrol URLQuery SSL Labs Stored certificate dates valid WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

3 evidence signal groups linked 0 stored notification records Last known active

Listed domains receive at least one abuse report; this entry has no retained notification history.

If credentials were compromised, report immediately. Do not engage with recovery scammers.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Immediate steps Find reporting contacts

Official reporting routes

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
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 →

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

Template-based draft · optional AI wording assistance requires separate consent

Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
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.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

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 elab-stilth.surge.sh)
  • 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

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

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

Live Threat Feed Appeal This Listing
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.

Request a correction or appeal How PhishDestroy works
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/elab-stilth.surge.sh"
  title="PhishDestroy threat report for elab-stilth.surge.sh"
  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>