Skip to security report
happybirthday210.top favicon
Domain security and threat intelligence

happybirthday210.top

I was scammed — help me write a report
Share / download report
Post on X Send in Telegram Check via API
In short

On 2026-11-18, happybirthday210.top displayed a dark-themed page featuring Telegram and Telegram Premium branding elements with a birthday promotional interface. Russian text on the page claims that a special gift of three months of Telegram Premium has been prepared for the user's birthday and asks them to activate it within twenty-four hours using a purple activation button labeled in Russian.

Page title: “Google”

More about the sources
Recorded security signals

Stored VirusTotal result: 4/92 engines flagged. Malicious: 3. Suspicious: 1. Analysis time (as stored): 2026-11-06 16:58 UTC. Retrieved (as stored): 2026-11-18 02:32 UTC. Use caution — do not enter credentials or personal information.

VirusTotal detections: 4/92 Spamhaus DBL: spam domain Young domain: 20 days old
Registrar
United StatesNameSilo
Resolved IP
Finland78.153.139.88Global Connectivity Solutions LLP
Registered
2026-11-02
First seen by PhishDestroy
2026-11-18
Page captures
open gallery
Domain age
registered 2026-11-02 according to WHOIS
2026-11-18

Risk score, higher = worse · How this score works

What to do right now

Pick what happened and tick the steps as you go. The ticks are kept only in this browser.

Entered a password0/3
Paid or entered card or bank details0/2
Downloaded a file0/2
Shared a seed phrase or private key0/3
Approved token spending (approve / permit)0/3
Connected a wallet but signed nothing0/2
Sent crypto0/3
Write a police report

Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.

Analysis

Domain summary

PhishDestroy first recorded happybirthday210.top on 2026-11-18. Stored VirusTotal result: 4/92 engines flagged. Malicious: 3. Suspicious: 1. Analysis time (as stored): 2026-11-06 16:58 UTC. Retrieved (as stored): 2026-11-18 02:32 UTC. Risk: critical (evidence score 80/100). Registrar: NameSilo. Status: Last known active. Hosting: GLOBAL CONNECTIVITY SOLUTIONS LLP. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
4 / 92
Hosting
Finland78.153.139.88Global Connectivity Solutions LLP
Registrar
United StatesNameSilo
Registered
2026-11-02
Page captures
4

URLScan capture · 2026-11-18 01:53 UTC · SHA-256 78e95d5c…8186c44

PhishDestroy analysis, reviewed version

On 2026-11-18, happybirthday210.top displayed a dark-themed page featuring Telegram and Telegram Premium branding elements with a birthday promotional interface. Russian text on the page claims that a special gift of three months of Telegram Premium has been prepared for the user's birthday and asks them to activate it within twenty-four hours using a purple activation button labeled in Russian.

The stored VirusTotal domain result reports 4 detections out of 92 engines. Webroot reported "malicious"; Fortinet reported "phishing".

Source evidenceVirusTotal 4 / 92 5 sources

VirusTotal

4 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 15 fields
Separate collector summary

This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.

Source
VirusTotal
Result state
observed
Numerator
4
Denominator
92
Vendors
alphaMountain.ai, Fortinet, SOCRadar, Webroot
Observed at
2026-11-06 16:58:37
Checked at
2026-11-18 03:32:24
Fetched at
2026-11-18 02:32:25

Spamhaus DBL

spam domain

URLScan

Malicious

SHA-256 cfb4f87e…815cb91

Open report
URLScanOriginal source recordObserved: 21 fields
Technical metadata

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

AI title
happybirthday210.top Telegram-branded birthday promotion
AI description
PhishDestroy publishes a factual review of happybirthday210.top showing a Telegram-branded promotional offer interface.
AI summary
On 2026-11-18, happybirthday210.top displayed a dark-themed page featuring Telegram and Telegram Premium branding elements with a birthday promotional interface. Russian text on the page claims that a special gift of three months of Telegram Premium has been prepared for the user's birthday and asks them to activate it within twenty-four hours using a purple activation button labeled in Russian. The stored VirusTotal domain result reports 4 detections out of 92 engines. Webroot reported "malicious"; Fortinet reported "phishing".
AI generated by
threat-v6-gemini
AI generated at
2026-11-18T02:57:24Z
Revision
b7834cf83c9bb0cc48ecd054d263836bf8d53f2de5edbfbf8317bfaa4d575b0a
Mode
reviewed
Interpretation
Selected public package; text generation time is separate from source observation dates.

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.

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 25 fields

Mail configuration

SPF lookups
0

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

Last observation
First observation
Recorded changes
0
Archived days
1
Average page size, bytes
484

Page title and metadata

Page title
Google

Trackers

Requests
12
Observed services
  • Name
    Google Static
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    4
  • Name
    Google Beacons
    Company
    Google
    Country
    US
    Category
    Site Analytics
    Requests
    3
  • Name
    Google CSP Reporting
    Company
    Google
    Country
    US
    Category
    Utilities
    Requests
    1

Forms and mixed content

Scripts without SRI
  • https://www.gstatic.com/og/_/js/k=og.asy.en_US.ZVAFwZQ0iIs.2019.O/rt=j/m=_ac,_awd,ada,lldp,qads,abld/exm=/d=1/ed=1/rs=AA2YrTt2KH-gaFRxm7nSeyfdPmRkuvCWQw
Third-party scripts
1

HTTP response

Reachable
Yes
HTTP status
302
Request timings, ms
DNS
0
Waiting
110
Download
1
Response time, ms
251

TLS connection

ALPN
h2
Cipher
TLS_AES_128_GCM_SHA256
Protocol
TLSv1.3
Supported versions
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 22
  • 80
  • 443

Carbon estimate

Bytes
200361
CO₂, grams
0.0073
Cleaner than, %
7

DNS servers

Nameservers
  • IP address
    162.159.38.194
    Host
    karsyn.ns.cloudflare.com
  • IP address
    108.162.195.15
    Host
    ezra.ns.cloudflare.com
DNS zone
happybirthday210.top

Page quality

Layout shift (CLS)
0
SEO score
91
Speed Index, s
1.83
First Contentful Paint (FCP), s
1.83
Largest Contentful Paint (LCP), s
1.83
Total Blocking Time (TBT), ms
205.5
Performance score
95
Accessibility score
98
Best practices score
100

Cookies

Cookies
  • Name
    PHPSESSID
    Secure
    Yes
    Session cookie
    Yes
    HTTP-only
    Yes
    SameSite
    None
  • Name
    __Secure-STRP
    Secure
    Yes
    SameSite
    Strict
  • Name
    SEARCH_SAMESITE
    SameSite
    Strict
  • Name
    AEC
    Secure
    Yes
    HTTP-only
    Yes
    SameSite
    Lax
  • Name
    NID
    Secure
    Yes
    HTTP-only
    Yes
    SameSite
    None

Location

IP address
78.153.139.88
ASN
215540
Organization
Global Connectivity Solutions LLP
City
Helsinki
Country
FI

TLS certificate

Subject alternative names
  • happybirthday210.top
Key size, bits
256
Certificate chain
  • happybirthday210.top
  • YE1
  • Root YE
  • ISRG Root X2
  • ISRG Root X1
Issuer
Let's Encrypt / YE1
Serial
05367D7C861AD91C797A0593088E542E7952
SHA-256
d8f823154e0029667c4aeefe042fa24519a55d54fa8b2b6fd09a6c4e0324125c
Subject
happybirthday210.top
Valid until
Valid from

DNS records

A
  • 78.153.139.88
NS
  • ezra.ns.cloudflare.com
  • karsyn.ns.cloudflare.com
SOA
Primary nameserver
ezra.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2419541366
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
SAMEORIGIN
Referrer-Policy
No
X-XSS-Protection
0
Permissions-Policy
unload=()
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
same-origin-allow-popups; report-to="gws"
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
78.153.139.88
IP version
4

Redirects

Redirect chain
  • https://happybirthday210.top
  • https://www.google.com
Count
1

Technology stack

Technologies
  • Google Web Server
  • Priority Hints
  • HTTP/3

Page links

External link addresses
  • https://mail.google.com/mail/&ogbl
  • https://www.google.com/imghp
  • https://www.google.com/intl/en/about/products
  • https://accounts.google.com/ServiceLogin
  • https://about.google/
  • https://www.google.com/intl/en_ir/ads/
  • https://www.google.com/services/
  • https://google.com/search/howsearchworks/
  • https://policies.google.com/privacy
  • https://policies.google.com/terms
  • https://www.google.com/preferences
  • https://support.google.com/websearch/
Internal link addresses
  • https://happybirthday210.top/advanced_search
  • https://happybirthday210.top/history/privacyadvisor/search/unauth
  • https://happybirthday210.top/history/optout
External links
12
Internal links
3

Registration record

Registrar
NameSilo,LLC
Registrar IANA ID
1479
Registrar URL
https://www.namesilo.com
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • ezra.ns.cloudflare.com
  • karsyn.ns.cloudflare.com
DNSSEC
unsigned

HTTP headers

Response headers
Server
gws
Content-Type
text/html; charset=UTF-8
X-Frame-Options
SAMEORIGIN
Permissions-Policy
unload=()
Cross-Origin-Opener-Policy
same-origin-allow-popups; report-to="gws"
Link
</shared_dict/homepage/6da693baa51a2e9a82e782cc621c5838bcaf35c9b6de3a17fec70c80564485d2.dict>; rel="compression-dictionary"
Original source fields · JSON
Mail configuration
Spf lookups: 0
Protective DNS results
Resolvers: 12; Blocked count: 0
Web archive observations
Last: 2026-11-02T12:57:29Z; First: 2026-11-02T12:57:29Z; Changes: 0; Days archived: 1; Avg page bytes: 484
Page title and metadata
Title: Google
Trackers
Requests: 12; Trackers: (Name: Google Static; Company: Google; Country: US; Category: Hosting; Requests: 4), (Name: Google Beacons; Company: Google; Country: US; Category: Site Analytics; Requests: 3), (Name: Google CSP Reporting; Company: Google; Country: US; Category: Utilities; Requests: 1)
Forms and mixed content
No sri: https://www.gstatic.com/og/_/js/k=og.asy.en_US.ZVAFwZQ0iIs.2019.O/rt=j/m=_ac,_awd,ada,lldp,qads,abld/exm=/d=1/ed=1/rs=AA2YrTt2KH-gaFRxm7nSeyfdPmRkuvCWQw; Third party scripts: 1
Status
Up: ✓; Code: 302; Timings: DNS: 0; Wait: 110; Download: 1; Response ms: 251
TLS connection
Alpn: h2; Cipher: TLS_AES_128_GCM_SHA256; Protocol: TLSv1.3; Versions: TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓
Ports
Open: 22, 80, 443
Carbon
Bytes: 200361; Co2 grams: 0.0073; Cleaner than: 7
DNS server
NS: (IP: 162.159.38.194; Host: karsyn.ns.cloudflare.com), (IP: 108.162.195.15; Host: ezra.ns.cloudflare.com); Zone: happybirthday210.top
Quality
Cls: 0; Seo: 91; Si s: 1.83; Fcp s: 1.83; Lcp s: 1.83; Tbt ms: 205.5; Performance: 95; Accessibility: 98; Best practices: 100
Cookies
Cookies: (Name: PHPSESSID; Secure: ✓; Session: ✓; HTTP only: ✓), (Name: __Secure-STRP; Secure: ✓; Same site: Strict), (Name: SEARCH_SAMESITE; Same site: Strict), (Name: AEC; Secure: ✓; HTTP only: ✓; Same site: Lax), (Name: NID; Secure: ✓; HTTP only: ✓)
Location
IP: 78.153.139.88; ASN: 215540; Org: Global Connectivity Solutions LLP; City: Helsinki; Country: FI
SSL
San: happybirthday210.top; Bits: 256; Chain: happybirthday210.top, YE1, Root YE, ISRG Root X2, ISRG Root X1; Issuer: Let's Encrypt / YE1; Serial: 05367D7C861AD91C797A0593088E542E7952; SHA256: d8f823154e0029667c4aeefe042fa24519a55d54fa8b2b6fd09a6c4e0324125c; Subject: happybirthday210.top; Valid to: 2027-01-31T11:49:36Z; Valid from: 2026-11-02T11:49:37Z
DNS records
A: 78.153.139.88; NS: ezra.ns.cloudflare.com, karsyn.ns.cloudflare.com; Soa: Nsname: ezra.ns.cloudflare.com; Hostmaster: dns.cloudflare.com; Serial: 2419541366; Refresh: 10000; Retry: 2400; Expire: 604800; Minttl: 1800
Dnssec
Ds: ✗; Rrsig: ✗; Dnskey: ✗
Hsts
Message: Site does not serve any HSTS headers.
HTTP security policies
Xframeoptions: SAMEORIGIN; Referrerpolicy: ✗; Xxssprotection: 0; Permissionspolicy: unload=(); Xcontenttypeoptions: ✗; Contentsecuritypolicy: ✗; Stricttransportpolicy: ✗; Crossoriginopenerpolicy: same-origin-allow-popups; report-to="gws"; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗
Get IP
IP: 78.153.139.88; Family: 4
Redirects
Chain: https://happybirthday210.top, https://www.google.com; Count: 1
Tech stack
Technologies: Google Web Server, Priority Hints, HTTP/3
Page links
External: https://mail.google.com/mail/&ogbl, https://www.google.com/imghp, https://www.google.com/intl/en/about/products, https://accounts.google.com/ServiceLogin, https://about.google/, https://www.google.com/intl/en_ir/ads/, https://www.google.com/services/, https://google.com/search/howsearchworks/, https://policies.google.com/privacy, https://policies.google.com/terms, https://www.google.com/preferences, https://support.google.com/websearch/; Internal: https://happybirthday210.top/advanced_search, https://happybirthday210.top/history/privacyadvisor/search/unauth, https://happybirthday210.top/history/optout; External count: 12; Internal count: 3
Registration record
Registrar: NameSilo,LLC; Registrar iana ID: 1479; Registrar URL: https://www.namesilo.com; Created: 2026-11-02T12:41:35Z; Updated: 2026-11-02T12:41:38Z; Expires: 2027-11-02T12:41:35Z; Status: clientTransferProhibited https://icann.org/epp; Nameservers: ezra.ns.cloudflare.com, karsyn.ns.cloudflare.com; Dnssec: unsigned
HTTP headers
Headers: Server: gws; Content type: text/html; charset=UTF-8; X frame options: SAMEORIGIN; Permissions policy: unload=(); Cross origin opener policy: same-origin-allow-popups; report-to="gws"; Link: </shared_dict/homepage/6da693baa51a2e9a82e782cc621c5838bcaf35c9b6de3a17fec70c80564485d2.dict>; rel="compression-dictionary"
Network Security Intelligence Registrar context
Registrar context NameSilo
Stored registration data identifies NameSilo as the registrar. PhishDestroy maintains separate registrar investigations; that broader material is contextual and is not an independent detection for this domain.
Review source investigation

Questions about happybirthday210.top

Is happybirthday210.top legit?

PhishDestroy rates happybirthday210.top as critical risk (evidence score 80/100) from the recorded evidence; it was first recorded on 2026-11-18. Stored VirusTotal result: 4/92 engines flagged. Malicious: 3. Suspicious: 1. Analysis time (as stored): 2026-11-06 16:58 UTC. Retrieved (as stored): 2026-11-18 02:32 UTC. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is happybirthday210.top safe to connect a wallet?

Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on happybirthday210.top. A confirmed blockchain transaction cannot be reversed.

What should I do if I used happybirthday210.top?

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
  • Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
  • Approved token spending (approve / permit) — revoke that approval with a token-approval checker
  • Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
  • Downloaded a file — do not open it and scan the device with security software

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.

Explore

Extracted from stored page analysis

Observed indicators

0 wallet · 1 Telegram

Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.

Telegram
https://t.me/telegramStored page reference

IoC extraction recorded 2026-11-18 05:00 UTC

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Page captures (4)

All capture links and hashes (4)
Observed page title
Google
TLS Certificate
Issued by YE1 · stored validity ends in 69 days

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Telegram report ↗
IP Reputation Finland78.153.139.88 0/100abuse score · abuse reports about this server's IP address, not about the domain; higher = worse This IP address has not been reported to the abuse database yet, but the domain itself is recognized as phishing. 0 reports checked 2026-11-18
RegistrationCreated 2026-11-02 (20d · Very New!) — Expires 2027-11-02
Registrant3432650ec337c9453432650ec337c945s@ VirusTotal WHOIS
HTTP Status302 Found (Temporary)
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First Detected2026-11-18
DOM Analysisanalyzed 2026-11-18score 0/100
IoC Extractionscanned 2026-11-180 wallet · 1 Telegram IoC
Submitted URLhttps://happybirthday210.top/9828d02c991970d4a57e40d57a95c419
ICANN OVERSIGHT

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

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.

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.

Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
Finland78.153.139.88
Network ASN
AS215540
Organization
Global Connectivity Solutions LLP
Observed location
FinlandHelsinki, FI

Nameservers 2

  • ezra.ns.cloudflare.com
  • karsyn.ns.cloudflare.com

SOA

  • nsname: ezra.ns.cloudflare.com
  • hostmaster: dns.cloudflare.com
  • serial: 2419541366
  • refresh: 10000
  • retry: 2400
  • expire: 604800
  • minttl: 1800

Registrar abuse contact VirusTotal WHOIS

Location describes the IP network.

TLS certificate

Issuer
YE1
Valid from
2026-11-02 11:49:37
Valid until
2027-01-31 11:49:36
Hostname match
Yes
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintd8f823154e0029667c4aeefe042fa24519a55d54fa8b2b6fd09a6c4e0324125c
Certificate names · 1 SAN
  • happybirthday210.top

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

Latest Classified Outcome 2026-11-22 11:14 UTC

The site was redirecting visitors elsewhere at the latest check.

Technical details
Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting DNS: Resolved
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-11-22 11:14 UTC
RDAP registration
Observed timeline last reachable: 2026-11-22 11:14 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.
Recorded subdomains10

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • aurora.happybirthday210.topDomain record
  • flora.happybirthday210.topDomain record
  • kws1.happybirthday210.topDomain record
  • kws2.happybirthday210.topDomain record
  • kws3.happybirthday210.topDomain record
  • kws4.happybirthday210.topDomain record
  • kws5.happybirthday210.topDomain record
  • pluto.happybirthday210.topDomain record
  • venus.happybirthday210.topDomain record
  • vesta.happybirthday210.topDomain record
Technologies · 3 identified
Open complete records

VirusTotal Analysis

4 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive result retrieved by PhishDestroy
Webroot
Fortinet
SOCRadar
alphaMountain.ai
PageSpeed (mobile): 97

Google PageSpeed Insights — mobile performance audit of happybirthday210.top ·

97
Good
Performance
FCP
1.51 s
First Contentful Paint
LCP
1.51 s
Largest Contentful Paint
CLS
0.023
Cumulative Layout Shift
TBT
197 ms
Total Blocking Time
SI
1.61 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: https://happybirthday210.top/9828d02c991970d4a57e40d57a95c419
Te​legram
Response
HTTP 200
HTML body
19.2 KB
Compressed
7.7 KB
Links
1 internal · 9 external
Detected technologies
wordpress
Selected response headers
Cache-Control: no-store, no-cache, must-revalidate
Content-Encoding: gzip
Content-Type: text/html; charset=UTF-8
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 8
Cache-Control
no-store, no-cache, must-revalidate
Content-Encoding
gzip
Content-Type
text/html; charset=UTF-8
Date
Wed, 18 Nov 2026 01:59:07 GMT
Expires
Thu, 19 Nov 1981 08:52:00 GMT
Pragma
no-cache
Transfer-Encoding
chunked
Vary
Accept-Encoding

Values retained by the collector; long values may be shortened during collection.

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.

All stored data106
Open complete records

Captured network requests

Network requests: 6 SHA-256 hashes: 3 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-18 01:55 UTC.

Open this scan on URLScan 01a1ec5c-0e4f-77d5-8b94-cd94be76af9d ↗

Stored observation history6

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

    Redirecting elsewhere

    HTTP redirect

  2. Availability monitor · Recorded state

    Redirecting elsewhere

    HTTP redirect

  3. Availability monitor · Recorded state

    Redirecting elsewhere

    HTTP redirect

  4. Availability monitor · Recorded state

    Redirecting elsewhere

    HTTP redirect

  5. Availability monitor · Recorded state

    Redirecting elsewhere

    HTTP redirect

Earlier observations 1
  1. Domain monitor · First collection record

    Reachable

Separate monitor HTTP observation

Source: domain_monitor. This stored snapshot does not establish current availability.

Observed · UTC
Recorded HTTP status
302
Probe value as recorded
302
Original source timestamp
2026-11-07 18:28:36
All retained availability observations14
Open complete records

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Monitoring · in progress

Recorded events: 11. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Pre-emptive Discovery & IngestionThreat Ingested recorded
  • Threat Ingested
    happybirthday210.top detected and queued for full analysis
Threat Intelligence ChecksSpamhaus DBL · URLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Registrar Context: NameSilo · Automated brand label: Google · Forensic Evidence Collected · Technical Analysis Recorded recorded
Publication & AvailabilityDestroyList Published · Monitoring Continues ongoing
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.
    ongoing

Recorded activity

3 entries

Lifecycle

  1. Domain registered
  2. VirusTotal analysis with detections+4 d 4 h
  3. Added to PhishDestroy+11 d 8 h
  1. Added to PhishDestroy

    happybirthday210.top

    same minute
  2. URLScan

    Page captured

    +11 d 8 h
  3. VirusTotal

    4/92 engine detections

How we investigate & report

Public scans, evidence and abuse channels

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.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

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.

All stored records by source

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

Check for cloaking

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

happybirthday210.top

Evidence & External Reports

Deep Analysis

Were You Affected by This Site?

You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Secure your accounts and funds first, then report. If credentials were compromised, report immediately. Do not engage with recovery scammers.

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.

Where to report

The draft stays only with you.

First secure your money: call your bank or revoke wallet approvals. Immediate steps →

More: international and crypto channels

Official reporting routes

More official reporting routes
SEAL 911 Worldwide

Emergency help from security researchers when a crypto wallet is being drained right now.

FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

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.

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
  • Downloaded a file — do not open it and scan the device with security software
  • Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
  • Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
  • Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
  • Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed

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 happybirthday210.top)
  • 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

Stay Informed, Stay Safe

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

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

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/happybirthday210.top"
  title="PhishDestroy threat report for happybirthday210.top"
  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>