Skip to security report
Analytics Dashboard
Domain security and threat intelligence
webiostart.readme.io favicon

webiostart.readme.io

In short

webiostart.readme.io is a Google impersonation page detected by PhishDestroy on 2026-09-17. Risk: critical (80/100). Registrar: 1API. Status: Last known active. Hosting: Cloudflare, Inc. VirusTotal: 5/91 engines flag it. Do not enter credentials or connect a wallet.

“webiostart”

Registrar
1API
Resolved IP
104.16.241.118
Registered
May 17, 2011
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
Risk signals
VirusTotal detections: 5/91 Automated brand label: Google
Sep 17, 2026 CDN
API
This domain has been flagged as malicious
Security engines reporting a detection: 5. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
5 / 91
engine detections
Google Safe Browsing
No threat flag
Page captures
2
open gallery
Domain age
5637 days
Source evidenceVirusTotal 5 / 91 4 sources

VirusTotal

5 / 91 engine detections

Open report

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

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

Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Phishing Security threats Phishing
View full Cloudflare Radar report

Analysis

Critical
VirusTotal
5 / 91
Page captures
2
Page captures Source results Registration record

PhishDestroy threat report

Overview

webiostart.readme.io is an impersonation phishing page built on a subdomain of readme.io, a documentation hosting platform. Its page title is simply "webiostart", which presents it as an official setup or getting-started guide. PhishDestroy first detected it on 2026-09-17. On 2026-10-19 the site was still alive and redirecting visitors onward.

How the scam works

Impersonation pages like this borrow the look and tone of a legitimate onboarding or support guide so the visitor trusts the instructions. The "webiostart" title frames the page as a first step, and the redirect then moves the visitor to wherever the operator collects input. In schemes of this kind, that input is usually account credentials, one-time codes, or a wallet recovery phrase, and anyone who supplies it loses control of the account or funds behind it. The page title does not name a specific brand, but we classify the page as impersonation phishing.

Evidence

On 2026-10-01, 5 of 91 VirusTotal engines flagged the address: alphaMountain.ai, Emsisoft, Forcepoint ThreatSeeker, Fortinet and Netcraft. That count is low, so most browsers and filters will not warn users. The five flags come from separate vendors, though, and they match PhishDestroy's own listing.

Infrastructure

The 2011-05-17 registration date through 1API GmbH belongs to the shared readme.io parent domain. It says nothing about when this page was created. Because the page sits on a trusted documentation platform, it inherits that platform's reputation, and domain-age checks will not catch it. Traffic is served through Cloudflare, Inc. from an address located in Canada, behind a standard Google Trust Services certificate.

What to do

If you followed this page and typed a password, change it right away on the real service and on any other account that uses the same one. Then turn on app-based two-factor authentication. If you entered a recovery phrase or private key, treat that wallet as compromised and move any remaining funds to a newly created wallet. Defenders should block the full subdomain rather than readme.io as a whole and report the page to the platform's abuse team. They should also check proxy logs for users who reached it after 2026-09-17.

Useful links

VirusTotal reportGoogle Safe Browsing statusReport phishing to GoogleSite owner? Request a review

Collected source details

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

Cloudflare Radar · 2026-09-25T04:47:49Z

Observed: · Retrieved:

Uuid
5de43bf5-29ac-4384-8999-b8756dfaa2d8
Final url
https://webiostart.readme.io/inactive
Status
401
Redirected
same-domain
History
[
    {
        "url": "https://webiostart.readme.io/",
        "status": 302
    },
    {
        "url": "https://webiostart.readme.io/inactive",
        "status": 401
    }
]
DOM structure hash
98320ca057e84299166cc9c91b98206dd50ca6f5f7a2a1b2d2100fe21149f845
Document hash
86a2689195f9fd6f6afa89483e3880f71916db2b8dc80cd3ed08dc0053c3d8fd
Domain risks
[
    "Phishing",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "cdn.readme.io",
        "type": "CNAME",
        "value": "ssl.readmessl.com"
    },
    {
        "name": "cdn.readme.io",
        "type": "CNAME",
        "value": "ssl.readmessl.com"
    },
    {
        "name": "webiostart.readme.io",
        "type": "CNAME",
        "value": "cname.readmessl.com"
    },
    {
        "name": "webiostart.readme.io",
        "type": "CNAME",
        "value": "cname.readmessl.com"
    }
]
Dnssec valid
false
Ip
104.16.241.118
Verdict
{
    "tags": [
        "phishing"
    ],
    "malicious": true,
    "categories": [
        "phishing"
    ]
}
Registration record
{
    "registrar": "1API GmbH",
    "created": "2011-05-17T10:06:31Z",
    "updated": "2026-08-12T10:17:07Z",
    "expires": "2027-05-17T10:06:31Z",
    "nameservers": [
        "uma.ns.cloudflare.com",
        "jeremy.ns.cloudflare.com"
    ]
}
VirusTotal · 2026-10-21T11:08:39Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 52,
    "malicious": 5,
    "suspicious": 0,
    "undetected": 35
}
Vendor labels
{
    "Emsisoft": "phishing",
    "Fortinet": "phishing",
    "Netcraft": "malicious",
    "alphaMountain.ai": "malicious",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Registrar
1API GmbH
Created
2011-05-17T10:06:31Z
Expires
2027-05-17T10:06:31Z
Updated
2026-08-12T10:17:07Z
First seen
2026-09-17T10:15:47Z
DNS records
[
    {
        "ttl": 300,
        "type": "CAA",
        "value": "ssl.com"
    },
    {
        "ttl": 300,
        "type": "CAA",
        "value": "pki.goog;"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700::6810:f276"
    },
    {
        "ttl": 300,
        "type": "CAA",
        "value": "comodoca.com"
    },
    {
        "ttl": 300,
        "type": "CAA",
        "value": "ssl.com"
    },
    {
        "ttl": 300,
        "type": "CAA",
        "value": "pki.goog;"
    },
    {
        "ttl": 300,
        "type": "CAA",
        "value": "comodoca.com"
    },
    {
        "ttl": 120,
        "type": "CNAME",
        "value": "cname.readmessl.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.16.241.118"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.16.242.118"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700::6810:f176"
    },
    {
        "ttl": 300,
        "type": "CAA",
        "value": "letsencrypt.org"
    },
    {
        "ttl": 300,
        "type": "CAA",
        "value": "letsencrypt.org"
    },
    {
        "ttl": 300,
        "type": "CAA",
        "value": "digicert.com"
    },
    {
        "ttl": 300,
        "type": "CAA",
        "value": "digicert.com"
    }
]
Dns at
2026-10-21T11:08:54Z
Jarm
27d27d27d00027d00042d43d00041df04c41293ba84f6efe3a613b22f983e6
Certificate
{
    "san": [
        "readme.io",
        "*.readme.io"
    ],
    "issuer": "Google Trust Services / WE1",
    "serial": "3b6df4b000c463020e342c94488fa3a1",
    "sha256": "52054a9ca28442ddb0ee75f981b79aebecbf2e9ee1749e6243e6439680556ef5",
    "subject": "readme.io",
    "valid_to": "2026-12-07T17:48:12Z",
    "valid_from": "2026-09-08T16:48:24Z"
}
Registration record
{
    "registrar": "1API GmbH",
    "registrar_iana_id": "1387",
    "registrar_url": "http://www.1api.net",
    "created": "2011-05-17T10:06:31Z",
    "updated": "2026-08-12T10:17:07Z",
    "expires": "2027-05-17T10:06:31Z",
    "status": [
        "clientTransferProhibited"
    ],
    "nameservers": [
        "jeremy.ns.cloudflare.com",
        "uma.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}

Questions about webiostart.readme.io

Is webiostart.readme.io legit?

No. PhishDestroy classifies webiostart.readme.io as a Google impersonation page (risk: critical, 80/100); it was first detected on 2026-09-17. VirusTotal: 5/91 engines flag it. Treat the site as unsafe.

Is webiostart.readme.io safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on webiostart.readme.io. 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 webiostart.readme.io?

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 · 2 captures

Cloudflare Radar 1 / 2
SourceCloudflare Radar
Recorded2026-09-25 04:47 UTC
StateStored capture
Position1 / 2
Open capture Source Report Wayback Download

Domain details

Domain
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar (base domain) 1API DE(DE)
Abuse contact["abuse@1api.net", "fb6ff66ef97c0518s@"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for readme.io →
Registration (base domain)readme.io · Created May 17, 2011 — Expires May 17, 2027
HTTP Status302 Found (Temporary)
Technical detailsProvenance & timestamps
First DetectedSep 17, 2026
Favicon Hash
Observed page title
webiostart
Automated brand references
Google
TLS Certificate
Issued by Google Trust Services / WE1 · stored validity ends in 45 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
104.16.241.118
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 1

  • jeremy.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WE1
Valid from
2026-09-08 16:48:24
Valid until
2026-12-07 17:48:12
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-09-23 13:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprint52054a9ca28442ddb0ee75f981b79aebecbf2e9ee1749e6243e6439680556ef5
Certificate names · 1 SAN
  • readme.io

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

viewdns.info · 104.16.241.118rapiddns.io

Latest Classified Outcome 2026-10-22 10:30:01 UTC

Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-10-22 10:30:01 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-22 10:30:01 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.
Technologies · 6 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

5 / 91 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 5 detections
alphaMountain.ai
Emsisoft
Forcepoint ThreatSeeker
Fortinet
Netcraft
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of webiostart.readme.io · checked Sep 25, 2026

99
Good
Performance
FCP
1.67s
First Contentful Paint
LCP
1.67s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.67s
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.

Stored observation history18

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→redirected

    http_redirect

  2. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  3. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  4. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  5. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

Earlier observations 13
  1. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  2. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  3. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  4. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  5. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  6. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  7. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  8. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  9. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  10. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  11. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  12. Availability monitor · Recorded state

    redirected

    http_redirect

  13. Availability monitor · First collection record

    Reachable

Recorded activity

3 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    5/91 engine detections

    View source
  3. Added to PhishDestroy

    webiostart.readme.io

    View source

Check for cloaking

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

webiostart.readme.io

Evidence & External Reports

Security Analysis
VirusTotal 5 det. ChainPatrol URLQuery SSL Labs Certificate hostname mismatch CF Radar Malicious 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?

2 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 webiostart.readme.io)
  • 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.

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.

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/webiostart.readme.io"
  title="PhishDestroy threat report for webiostart.readme.io"
  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>