Skip to security report
Domain security and threat intelligence
brendanjosephsmith.com favicon

brendanjosephsmith.com

In short

brendanjosephsmith.com is a phishing page detected by PhishDestroy on 2026-10-23. Risk: critical (98/100). Registrar: ENOM. Hosting: DigitalOcean, LLC. PhishDestroy sent 1 abuse report. VirusTotal: 16/92 engines flag it. Do not enter credentials or connect a wallet.

“brendanjosephsmith.com”

Registrar
ENOM
Resolved IP
46.101.71.127
Registered
Apr 24, 2018
PhishDestroy assessment Critical
First observed Oct 23, 2026 14:32 UTC · PhishDestroy
VirusTotal detections: 16/92
OTX: 5 refs Oct 23, 2026 1 Report Sent
API
This domain has been flagged as malicious
Security engines reporting a detection: 16. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Page captures
open gallery
Domain age
Reports sent
view timeline
Source evidenceVirusTotal 16 / 92 · OTX 5 references 6 sources

VirusTotal

16 / 92 engine detections

Open report

OTX

5 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
Malware Malware Security threats

Collected source details

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

URLScan · 2026-10-23T14:31:17Z

Observed: · Retrieved:

Uuid
01a1692c-1278-734f-98b8-5658c786f6a0
Final url
https://brendanjosephsmith.com/egypt/aswan
Status
200
Redirected
same-domain
Redirects
[
    {
        "to": "https://brendanjosephsmith.com/",
        "from": "http://brendanjosephsmith.com/",
        "status": 307
    },
    {
        "to": "https://brendanjosephsmith.com/egypt/aswan",
        "from": "https://brendanjosephsmith.com/",
        "status": 307
    }
]
Ip
46.101.71.127
Contacted domains
[
    "interactive-examples.mdn.mozilla.net"
]
Contacted IP addresses
[
    "34.111.242.42",
    "46.101.71.127"
]
Asns
[
    "396982",
    "14061"
]
Countries
[
    "US",
    "DE"
]
Document hash
6005b5b1d68121b18fed7033f15c42197f05720102e880f5a277d99264c10319
Script hashes
[
    "7e1f5b1b3270805286c5146e81fb84c9bb523df5ad64b3f4cbf6dd26c7df1cad",
    "1f41d81e50a4ed03321b90588b599529026467cf7b4ab37d2fecb317c244be3a",
    "c97d9b98fef70ce495f470ac4ada8718f64695bb812af8c13c26bf236029fb62",
    "baf33bb6ac09158bcf6b201dd14185dc14625760247a26f2afff362ea62ad53b",
    "17d2cd1ac9c7d8bf81aeafb168243568db48289959d677ce7fae7812ea0c9ef6",
    "c4c0212f03ac702b8a1e8cfb1ca33455039062606646544cc7fe87561d6b534c",
    "2f16f6667c9317f4421c0a5daf2cef013822be415697153b1887a3c7dd3d4fd7",
    "6ac5245f35cc5e6b97be2770688033d735db44ed962176ad3e17056ef9292b4e",
    "a83dd033e497e4960b662ffa7225d33db9ccb2ea106c46bcd21f6d31490dd9d8",
    "a8a908a2a0a5f033dee8ecb66f01f4c88e8941d352aa8bc013ff1dd618eefd9a"
]
Globals
[
    "__next_s",
    "__next_f",
    "$RT",
    "$RS",
    "$RB",
    "$RV",
    "$RC",
    "TURBOPACK",
    "next",
    "__webpack_hash__",
    "__APP_RUNTIME_CONFIG__",
    "__zod_globalConfig",
    "__zod_globalRegistry"
]
Cookies
[
    "NEXT_LOCALE"
]
Tls
{
    "san": [
        "ingress.local"
    ],
    "cipher": "AES_256_GCM",
    "issuer": "Kubernetes Ingress Controller Fake Certificate",
    "subject": "Kubernetes Ingress Controller Fake Certificate",
    "protocol": "TLS 1.3",
    "valid_to": "2027-06-28T08:58:53Z",
    "valid_from": "2026-06-28T08:58:53Z"
}
Domain age days
1827
Apex age days
1827
Tls age days
117
Tls valid days
365
Requests
44
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 79,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "content-type": "text/html; charset=utf-8",
    "x-powered-by": "Next.js",
    "strict-transport-security": "max-age=31536000; includeSubDomains"
}
Cloudflare Radar · 2026-10-23T15:10:02Z

Observed: · Retrieved:

Uuid
02f59447-5105-4092-b5f9-3c6a63a835e4
Final url
https://brendanjosephsmith.com/
History
[
    {
        "url": "https://brendanjosephsmith.com/",
        "status": 0
    }
]
DOM structure hash
94bfc7c24186e5b245b5675859fb84b248547086370961e5637590177432b219
Domain risks
[
    "Malware",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "brendanjosephsmith.com",
        "type": "A",
        "value": "46.101.71.127"
    }
]
Dnssec valid
false
Verdict
{
    "tags": [
        "malware"
    ],
    "malicious": true,
    "categories": [
        "malware"
    ]
}
Registration record
{
    "registrar": "eNom, LLC",
    "created": "2018-04-24T16:58:19Z",
    "updated": "2026-04-23T08:06:58Z",
    "expires": "2027-04-24T16:58:19Z",
    "nameservers": [
        "ns1.greengeeks.net",
        "ns2.greengeeks.net"
    ]
}
VirusTotal · 2026-10-18T17:47:58Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 44,
    "malicious": 13,
    "suspicious": 3,
    "undetected": 32
}
Vendor labels
{
    "DNS8": "suspicious",
    "ESET": "suspicious",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "suspicious",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Tags
[
    "self-signed"
]
Categories
{
    "Google": "real_estate",
    "Sophos": "phishing and fraud",
    "Webroot": "Phishing and Other Frauds",
    "BitDefender": "realestate",
    "alphaMountain.ai": "Phishing (alphaMountain.ai)"
}
Registrar
ENOM, INC.
Created
2018-04-24T16:58:19Z
Expires
2027-04-24T16:58:19Z
Updated
2026-10-18T17:53:20Z
First seen
2026-05-14T09:33:32Z
DNS records
[
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns1.greengeeks.net"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns2.greengeeks.net"
    },
    {
        "ttl": 14400,
        "type": "MX",
        "value": "brendanjosephsmith.com",
        "priority": 0
    },
    {
        "ttl": 21600,
        "type": "SOA",
        "rname": "root.sgp200.greengeeks.net",
        "value": "ns1.greengeeks.net"
    },
    {
        "ttl": 14400,
        "type": "TXT",
        "value": "v=spf1 +a +mx +ip4:23.106.55.197 include:spf.greengeeks.net ~all"
    },
    {
        "ttl": 14400,
        "type": "A",
        "value": "46.101.71.127"
    }
]
Dns at
2026-10-18T17:53:23Z
Jarm
29d29d00029d29d00042d42d00000023f2ae7180b8a0816654f2296c007d93
Certificate
{
    "san": [
        "ingress.local"
    ],
    "issuer": "Acme Co / Kubernetes Ingress Controller Fake Certificate",
    "serial": "a8fcf764d53b04210e5611568e6f2325",
    "sha256": "7d605012818ef17a09ceb89e9def648ca88b89ba3753c705c28d7715cd6f3836",
    "subject": "Kubernetes Ingress Controller Fake Certificate",
    "valid_to": "2027-06-28T08:58:53Z",
    "valid_from": "2026-06-28T08:58:53Z"
}
Registration record
{
    "registrar": "ENOM, INC.",
    "registrar_iana_id": "48",
    "registrar_url": "WWW.ENOMDOMAINS.COM",
    "created": "2018-04-24T16:58:00Z",
    "updated": "2026-04-23T08:06:58Z",
    "expires": "2027-04-24T16:58:19Z",
    "status": [
        "clientTransferProhibited"
    ],
    "nameservers": [
        "ns1.greengeeks.net",
        "ns2.greengeeks.net"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "client transfer prohibited"
    ],
    "events": {
        "last changed": "2026-10-15T23:35:52Z",
        "registration": "2018-04-24T16:58:00Z",
        "registrar expiration": "2027-04-24T16:58:19Z",
        "last update of RDAP database": "2026-10-15T23:35:52Z"
    }
}
Website checks · 2026-10-23T15:11:17Z
Mail configuration
{
    "mx": [
        "brendanjosephsmith.com"
    ],
    "spf": "v=spf1 +a +mx +ip4:23.106.55.197 include:spf.greengeeks.net ~all",
    "dkim": [
        "default"
    ],
    "dmarc": true,
    "dkim_bits": 2048,
    "spf_lookups": 4
}
Caa records
{
    "domain": "brendanjosephsmith.com"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2021-12-16T20:43:03Z",
    "first": "2021-11-26T08:52:26Z",
    "changes": 1,
    "days_archived": 2,
    "scans_per_day": 0.05,
    "avg_page_bytes": 1175
}
Trackers
{
    "requests": 50
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": false,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443
    ]
}
Dns server
{
    "ns": [
        {
            "ip": "75.2.69.7",
            "host": "ns1.greengeeks.net"
        },
        {
            "ip": "99.83.188.187",
            "host": "ns2.greengeeks.net"
        }
    ],
    "zone": "brendanjosephsmith.com"
}
Location
{
    "ip": "46.101.71.127",
    "asn": "14061",
    "org": "DigitalOcean, LLC",
    "city": "Frankfurt am Main",
    "country": "DE"
}
Ssl
{
    "issuer": "Acme Co / Kubernetes Ingress Controller Fake Certificate",
    "subject": "Kubernetes Ingress Controller Fake Certificate"
}
DNS records
{
    "A": [
        "46.101.71.127"
    ],
    "MX": [
        "{\"exchange\": \"brendanjosephsmith.com\", \"priority\": 0}"
    ],
    "NS": [
        "ns1.greengeeks.net",
        "ns2.greengeeks.net"
    ],
    "SOA": "{\"nsname\": \"ns1.greengeeks.net\", \"hostmaster\": \"root.sgp200.greengeeks.net\", \"serial\": 2026051406, \"refresh\": 3600, \"retry\": 1800, \"expire\": 1209600, \"minttl\": 86400}",
    "TXT": [
        "v=spf1 +a +mx +ip4:23.106.55.197 include:spf.greengeeks.net ~all"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Get ip
{
    "ip": "46.101.71.127",
    "family": 4
}
Tech stack
{
    "technologies": [
        "Node.js",
        "MUI",
        "Marko",
        "React",
        "Emotion",
        "Next.js",
        "Priority Hints",
        "HSTS",
        "Webpack",
        "Open Graph"
    ]
}
Registration record
{
    "registrar": "eNom, LLC",
    "created": "2018-04-24T16:58:19Z",
    "updated": "2026-04-23T08:06:58Z",
    "expires": "2027-04-24T16:58:19Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "ns1.greengeeks.net",
        "ns2.greengeeks.net"
    ]
}

Questions about brendanjosephsmith.com

Is brendanjosephsmith.com legit?

No. PhishDestroy classifies brendanjosephsmith.com as a phishing page (risk: critical, 98/100); it was first detected on 2026-10-23. VirusTotal: 16/92 engines flag it. Treat the site as unsafe.

Is brendanjosephsmith.com safe to connect a wallet?

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

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

Domain details

Domain
IP Reputation abuse score 0/100 0 reports checked Oct 23, 2026
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
RegistrationCreated Apr 24, 2018 — Expires Apr 24, 2027
Technical detailsProvenance & timestamps
First DetectedOct 23, 2026
Submitted URLhttp://brendanjosephsmith.com/
Favicon Hash
Case ID
Observed page title
brendanjosephsmith.com
TLS Certificate
Issued by Kubernetes Ingress Controller Fake Certificate · stored validity ends in 247 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
46.101.71.127
Network ASN
AS14061
Organization
DigitalOcean, LLC
Observed location
Frankfurt am Main, DE

Nameservers 2

  • ns1.greengeeks.net
  • ns2.greengeeks.net

Mail routing 1 MX record

  • brendanjosephsmith.compriority 0

Location describes the IP network.

TLS certificate

Issuer
Kubernetes Ingress Controller Fake Certificate
Valid from
2026-06-28 08:58:53
Valid until
2027-06-28 08:58:53
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint7d605012818ef17a09ceb89e9def648ca88b89ba3753c705c28d7715cd6f3836
Certificate names · 1 SAN
  • ingress.local

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

Report This Domain Submit evidence & help protect others

VirusTotal Analysis

16 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 16 detections
alphaMountain.ai
BitDefender
CyRadar
DNS8
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
Seclookup
SOCRadar
Sophos
VIPRE
Webroot
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of brendanjosephsmith.com · checked Oct 23, 2026

82
Needs Work
Performance
FCP
1.51s
First Contentful Paint
LCP
2.35s
Largest Contentful Paint
CLS
0.252
Cumulative Layout Shift
TBT
5ms
Total Blocking Time
SI
4.32s
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: http://brendanjosephsmith.com/
Final URL: http://brendanjosephsmith.com/egypt/aswan
Listings in Aswan | Salek
Browse trusted property and car listings in Aswan.
Response
HTTP 200
HTML body
220.6 KB
Compressed
47.5 KB
Links
9 internal · 0 external
Detected technologies
react
Selected response headers
Content-Type: text/html; charset=utf-8
X-Powered-By: Next.js
Cache-Control: private, no-cache, no-store, max-age=0, must-revalidate
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Favicon fingerprint: a733cbc6ec0c0edf7ecdf433244af6ef4eb114618980416e5d78c82aa00511c0
Open Graph title: Listings in Aswan | Salek
Open Graph description: Browse trusted property and car listings in Aswan.
Twitter card: summary_large_image
Saved response-header values · 10
Cache-Control
private, no-cache, no-store, max-age=0, must-revalidate
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Fri, 23 Oct 2026 14:33:18 GMT
Link
; rel="alternate"; hreflang="ar", ; rel="alternate"; hreflang="en", ; rel="alternate"; hreflang="x-default"
Transfer-Encoding
chunked
Vary
rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch, Accept-Encoding
x-middleware-rewrite
/en/egypt/aswan
X-Powered-By
Next.js

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

Registration & observation details1

Availability observations

Last reachable observation

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Stored observation history1

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · First collection record

    Reachable

Recorded activity

6 entries
  1. AlienVault OTX

    5 community references

    View source
  2. Google Safe Browsing

    No threat flag

    View source
  3. VirusTotal

    16/92 engine detections

    View source
  4. Abuse report sent

    PD-20261023-5E95A0

    abuse@enom.com
  5. Added to PhishDestroy

    brendanjosephsmith.com

    View source
  6. URLScan

    Page captured

    View source

Check for cloaking

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

brendanjosephsmith.com

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20261023-5E95A0 Recipient: abuse@enom.com
PDF notice generated Notice text archived (859 chars)
Abuse notice text as sent to the provider
AUP & Terms of Service Violations:
Acceptable Use Policy: Active phishing operations targeting internet users directly violate standard AUP provisions prohibiting fraud and deceptive practices.
Terms of Service: Material breach of service terms regarding malicious use, providing contractual justification for immediate suspension.
Applicable Legal Framework (US):
18 U.S.C. § 1343 - Wire Fraud
18 U.S.C. § 1030 - Computer Fraud and Abuse Act (CFAA)
15 U.S.C. § 45 - FTC Act (Deceptive Practices)
Federal laws prohibit wire fraud, computer fraud, and deceptive business practices.
Investigation Notice: We fully respect your internal investigation processes and discretion. Prompt remediation protects innocent users while mitigating regulatory compliance scrutiny, legal liability, and brand reputation risks associated with ongoing malicious infrastructure.
Deep Analysis
Help & reporting

Were You Affected by This Site?

6 evidence signal groups linked 1 stored notification records Unverified
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.

Official reporting routes

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 brendanjosephsmith.com)
  • 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

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.

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