Skip to security report
Analytics Dashboard
Domain security and threat intelligence
admin.foundation.byrds.dev favicon

admin.foundation.byrds.dev

In short

admin.foundation.byrds.dev is a Foundation impersonation page detected by PhishDestroy on 2026-09-08. Risk: critical (85/100). Registrar: OVH sas. Status: Last known active. Hosting: OVH OVH SAS, FR. PhishDestroy sent 1 abuse report. VirusTotal: 5/92 engines flag it. Do not enter credentials or connect a wallet.

“Foundation · Administration”

Registrar
OVH sas
Resolved IP
146.59.151.218
Registered
Oct 27, 2020
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
Risk signals
VirusTotal detections: 5/92 Stored blocklist matches: 2 Automated brand label: Foundation
Sep 8, 2026 1 Report Sent
API
This domain has been flagged as malicious
Security engines reporting a detection: 5. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
ABUSE NOTICE · 7D+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

The sent-report ledger records the first outgoing report at . The recorded recipient is abuse@ovh.net. The latest stored availability evidence still shows the domain reachable; 1 month has elapsed since the first outgoing report.

ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.

Elapsed since first report
1 month
Reports sent
1
Latest case ID
PD-20260908-455E40
Current status
HTTP 200 at latest stored check
VirusTotal
5 / 92
engine detections
Google Safe Browsing
No threat flag
Page captures
5
open gallery
Domain age
2186 days
Reports sent
1
view timeline
Source evidenceVirusTotal 5 / 92 6 sources

VirusTotal

5 / 92 engine detections

Open report

URLQuery

checked — no detections recorded

Open report

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.

Analysis

Critical
VirusTotal
5 / 92
Page captures
5
Page captures Source results Registration record

PhishDestroy threat report

Overview

admin.foundation.byrds.dev is an impersonation phishing page posing as Foundation. Its page title is "Foundation · Administration", so it presents itself as an internal admin console rather than the public site, and it targets people who use Foundation or hold crypto wallets. PhishDestroy first flagged it on 2026-09-08. As of 2026-10-19 the site was still alive and its content now redirects visitors elsewhere.

How the scam works

Impersonation pages like this borrow a trusted brand's name and look so visitors will act without second-guessing. An "Administration" label adds false authority. It can make a request to log in, verify an account or connect a wallet feel like official procedure. Whatever the victim types or approves goes to the operator, not to Foundation. Depending on what is entered, that can mean stolen account credentials, a leaked recovery phrase or a malicious wallet signature that moves assets out.

Evidence

Wallet-security blocklists back the classification. MetaMask and SEAL both list the domain alongside PhishDestroy, so users of those protections should already see a warning. Coverage on VirusTotal is thinner, with 5 of 89 engines flagging it as of 2026-09-22: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft and SOCRadar. That low count means many general-purpose security tools will still let the page load without a warning.

Infrastructure

The page sits on a subdomain of byrds.dev, which was registered on 2020-10-27 through OVH sas. That is nearly six years before PhishDestroy detected this page, so the age of the parent domain says little about how trustworthy this subdomain is. The site is hosted in France on the OVH SAS network at 146.59.151.218. Its certificate comes from Let's Encrypt, so the padlock in the browser only means the connection is encrypted, not that the site is genuine.

What to do

If you entered a Foundation login or email password here, change it now. Do the same anywhere you reused it, and turn on two-factor authentication. If you typed a seed or recovery phrase, treat that wallet as compromised and move your funds to a newly created wallet. If you connected a wallet or signed anything, check the token approvals on a revocation tool and revoke any you don't recognize. Defenders should block the full hostname, including future redirect targets from it, and add it to wallet and mail filtering, since most antivirus engines still don't flag it.

Useful links

urlscan.io scan and screenshotVirusTotal reportGoogle Safe Browsing statusArchived copyReport phishing to GoogleSite owner? Request a review

Collected source details

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

URLScan · 2026-09-08T09:59:13Z

Observed: · Retrieved:

Uuid
01a08075-0372-754a-89fa-1ba728bc61db
Final url
https://admin.foundation.byrds.dev/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://admin.foundation.byrds.dev/",
        "from": "http://admin.foundation.byrds.dev/",
        "status": 307
    }
]
Ip
146.59.151.218
Ptr
vps-3f658227.vps.ovh.net
Contacted IP addresses
[
    "146.59.151.218"
]
Asns
[
    "16276"
]
Countries
[
    "FR"
]
Linked domains
[
    "foundation.byrds.dev"
]
Document hash
b9aadcc6ecadf35b7022a2a04d9cd16c0733ba9ee5904b8fd4a63d303edc433a
Script hashes
[
    "853a466edd3d82da3e68b67122a9542b03981f24eee46c706b2da224a474747b",
    "848b0037fdae0e756eb091eb981f29c451eecadc7866dfee8bbcd6f584a5b31e",
    "e91810e5d0cf8d930d485e32bf41b9dc4cc9a1add9afdc14e149187a707a92fe"
]
Globals
[
    "$R",
    "nanostoresGlobal",
    "__zod_globalConfig",
    "__zod_globalRegistry",
    "__TSR_ROUTER__",
    "__TSS_START_OPTIONS__"
]
Tls
{
    "san": [
        "admin.foundation.byrds.dev",
        "app.foundation.byrds.dev",
        "foundation.byrds.dev"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE1",
    "subject": "admin.foundation.byrds.dev",
    "protocol": "TLS 1.3",
    "valid_to": "2026-12-06T21:15:41Z",
    "valid_from": "2026-09-07T21:15:42Z"
}
Domain age days
0
Apex age days
2141
Tls age days
0
Tls valid days
89
Requests
8
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 21,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "openresty",
    "content-type": "text/html; charset=utf-8"
}
Cloudflare Radar · 2026-09-08T10:02:16Z

Observed: · Retrieved:

Uuid
c8c1b676-cf5b-400f-9044-40c16dd7bb21
Final url
https://admin.foundation.byrds.dev/
Status
200
History
[
    {
        "url": "https://admin.foundation.byrds.dev/",
        "status": 200
    }
]
DOM structure hash
029d85b5144b314f660a608b0ab4cc781c5454f84fe0ccfee7c2c34d6b100dff
Document hash
40e6541809603faffed47004f0d9e815761f94889ba59a91cd0dc7b3ee3ce060
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "admin.foundation.byrds.dev",
        "type": "CNAME",
        "value": "byrds.dev"
    },
    {
        "name": "byrds.dev",
        "type": "A",
        "value": "146.59.151.218"
    },
    {
        "name": "admin.foundation.byrds.dev",
        "type": "CNAME",
        "value": "byrds.dev"
    }
]
Dnssec valid
false
Ip
146.59.151.218
VirusTotal · 2026-10-08T15:48:42Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 53,
    "malicious": 4,
    "suspicious": 1,
    "undetected": 34
}
Vendor labels
{
    "CRDF": "malicious",
    "SOCRadar": "phishing",
    "Gridinsoft": "suspicious",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Registrar
OVH sas
Created
2020-10-27T20:47:49Z
Expires
2025-10-27T20:47:49Z
Updated
2024-02-04T12:21:22Z
First seen
2026-09-07T22:35:56Z
DNS records
[
    {
        "ttl": 3600,
        "type": "NS",
        "value": "ns200.anycast.me"
    },
    {
        "ttl": 3600,
        "type": "A",
        "value": "146.59.151.218"
    },
    {
        "ttl": 3600,
        "type": "NS",
        "value": "dns200.anycast.me"
    },
    {
        "ttl": 3600,
        "type": "CNAME",
        "value": "byrds.dev"
    },
    {
        "ttl": 3600,
        "type": "SOA",
        "rname": "tech.ovh.net",
        "value": "dns200.anycast.me"
    }
]
Dns at
2026-10-09T09:33:23Z
Jarm
27d40d40d00040d00042d43d000000e1ea2a807a629b496b664cf07ad7c08d
Certificate
{
    "san": [
        "admin.foundation.byrds.dev",
        "app.foundation.byrds.dev",
        "foundation.byrds.dev"
    ],
    "issuer": "Let's Encrypt / YE1",
    "serial": "6a6a8dc476f29b8ece91ce5a6685e07fc96",
    "sha256": "60677b3b741b9786cbd70f7a2cf12793848d2967d101987c726d04a5c98b1e46",
    "subject": "admin.foundation.byrds.dev",
    "valid_to": "2026-12-06T21:15:41Z",
    "valid_from": "2026-09-07T21:15:42Z"
}
Registration record
{
    "registrar": "OVH sas",
    "registrar_iana_id": "433",
    "registrar_url": "https://www.ovh.com",
    "created": "2020-10-27T20:47:49Z",
    "updated": "2024-02-04T12:21:22Z",
    "expires": "2025-10-27T13:02:42Z",
    "status": [
        "clientDeleteProhibited",
        "clientTransferProhibited"
    ],
    "nameservers": [
        "dns200.anycast.me",
        "ns200.anycast.me"
    ],
    "dnssec": "unsigned"
}

Questions about admin.foundation.byrds.dev

Is admin.foundation.byrds.dev legit?

No. PhishDestroy classifies admin.foundation.byrds.dev as a Foundation impersonation page (risk: critical, 85/100); it was first detected on 2026-09-08. VirusTotal: 5/92 engines flag it. Treat the site as unsafe.

Is admin.foundation.byrds.dev safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on admin.foundation.byrds.dev. 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 admin.foundation.byrds.dev?

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 matchesMetaMask · PhishDestroy · SEAL 3
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Last checked

Stored Capture · 5 captures

Primary capture 1 / 5
SourcePrimary capture
Recorded2026-09-08 10:00 UTC
StateStored capture
Position1 / 5
Open capture Wayback Download
Observed page title
Foundation · Administration
Automated brand references
Foundation
TLS Certificate
Issued by Let's Encrypt · stored validity ends in 89 days

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Reputation abuse score 0/100 0 reports checked Oct 8, 2026
Registrar (base domain) OVH sas (Unknown)
Abuse contactabuse@ovh.net
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for byrds.dev →
Registration (base domain)byrds.dev · Created Oct 27, 2020 — Expires Oct 27, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedSep 8, 2026
DOM Analysisanalyzed Sep 8, 2026score 85/1001 brand signal
Submitted URLhttp://admin.foundation.byrds.dev/
Favicon Hash
Case ID
ICANN OVERSIGHT Registration: byrds.dev

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

For the registrable domain byrds.dev behind this subdomain, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.

Accreditation is a contract, not a safety certification.

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.

Accreditation is a contract, not a safety seal. Verify ICANN fees Read RAA §3.18 PHISHDESTROY INVESTIGATIONICANN funding, contracts, and DNS abuse oversight
Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
146.59.151.218
Network ASN
AS16276
Organization
OVH SAS
Observed location
Dunkirk, FR
Server header
openresty

Nameservers 2

  • dns200.anycast.me
  • ns200.anycast.me

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt
Valid from
2026-09-07 21:15:42
Valid until
2026-12-06 21:15:41
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-09-08 10:02:05 UTC
Collection source
PhishDestroy collector
Certificate fingerprint60677b3b741b9786cbd70f7a2cf12793848d2967d101987c726d04a5c98b1e46
Certificate names · 2 SANs
  • app.foundation.byrds.dev
  • foundation.byrds.dev

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

viewdns.info · 146.59.151.218rapiddns.io

Latest Classified Outcome 2026-10-23 10:32:12 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: Resolved Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-10-23 10:32:12 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-23 10:32:12 UTC last content: 2026-10-23 10:32:12 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 · 4 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

5 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 5 detections
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
Gridinsoft
SOCRadar

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of admin.foundation.byrds.dev · checked Sep 8, 2026

98
Good
Performance
FCP
1.8s
First Contentful Paint
LCP
1.8s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
2.76s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
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 history27

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 · Recorded state

    live_content→redirected

    http_redirect

  3. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  4. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  5. Availability monitor · Recorded state

    redirected→live_content

    content_served

Earlier observations 22
  1. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  2. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  3. Availability monitor · Recorded state

    redirected→live_content

    content_served

  4. Availability monitor · Recorded state

    live_content→redirected

    http_redirect

  5. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  6. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  7. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  8. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  9. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  10. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  11. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  12. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  13. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  14. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  15. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  16. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  17. VirusTotal · Detection count

    4→5

  18. VirusTotal · Detection count

    3→4

  19. VirusTotal · Detection count

    2→3

  20. VirusTotal · Detection count

    1→2

  21. VirusTotal · Detection count

    0→1

  22. Availability monitor · First collection record

    Reachable

Recorded activity

5 entries
  1. VirusTotal

    5/92 engine detections

    View source
  2. Google Safe Browsing

    No threat flag

    View source
  3. Abuse report sent

    PD-20260908-455E40

    abuse@ovh.net
  4. Added to PhishDestroy

    admin.foundation.byrds.dev

    View source
  5. URLScan

    Page captured

    View source

Check for cloaking

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

admin.foundation.byrds.dev

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 5 det. ChainPatrol URLQuery Report stored SSL Labs Certificate hostname mismatch CF Radar Open report WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20260908-455E40 Recipient: abuse@ovh.net
Page title stored with report: Foundation · Administration
PDF notice generated
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 Archived
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?

5 evidence signal groups linked 1 stored notification records Last known active
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 admin.foundation.byrds.dev)
  • 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/admin.foundation.byrds.dev"
  title="PhishDestroy threat report for admin.foundation.byrds.dev"
  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>