PhishDestroy added related.online-working.net to its internal blocklist after a manual review on 2026-10-21. The intake AI noted that the page content "Welcome - Related" is too generic to determine malicious intent or impersonation. The domain was first seen by PhishDestroy on 2026-10-21 and returned an HTTP 200 response on that date.
How the scam works
No specific malicious technique was observed on this page. Generic suspicious domains are sometimes used as landing pages for phishing, credential harvesting, or as placeholders for future fraudulent campaigns, but no evidence of such activity is present here.
Evidence
VirusTotal scanned the domain on 2026-10-15 and reported 0 malicious and 0 suspicious detections out of 92 engines. Google Safe Browsing checked the domain on 2026-10-21 and did not flag it. urlscan.io captured a clean verdict on 2026-10-06, and OTX listed 0 pulses as of 2026-10-21. No external blocklists reported the domain, while PhishDestroy’s internal list marks it as blocked as of 2026-10-21.
Infrastructure
The recorded IP for the domain is 38.127.8.167, which belongs to Ultahost, Inc. in Singapore. No registrar or CDN details are available beyond this network information.
What to do
If any credentials were entered on the site, change those passwords and monitor the associated accounts for unusual activity. Defenders should block traffic to related.online-working.net based on the PhishDestroy internal listing and review access logs for any connections to this exact address.
Registration (base domain)online-working.net · Created Sep 29, 2026 (22d · Very New!)—Expires Sep 29, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 21, 2026
DOM Analysisanalyzed Oct 21, 2026score 68/100
Submitted URLhttps://related.online-working.net/
Favicon Hash
Case ID
Observed page title
Welcome - Related
TLS Certificate
Issued by Let's Encrypt / YE2· stored validity ends in 73 days
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
38.127.8.167
Network ASN
AS44259
Organization
Ultahost, Inc.
Observed location
Singapore, SG
Server header
nginx/1.24.0 (Ubuntu)
Nameservers 4
ns1.ultahost.com
ns2.ultahost.com
ns3.ultahost.com
ns4.ultahost.com
Location describes the IP network.
TLS certificate
Issuer
Let's Encrypt / YE2
Valid from
2026-10-04 16:17:33
Valid until
2027-01-02 16:17:32
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint340f648b32ac4d370fcb7a586c8454fe803bb7180ec31e75e49f2d3bf6699b10Certificate names · 2 SANs
related.online-working.net
www.related.online-working.net
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
4 evidence signal groups linked1 stored notification recordsLast 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.
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 →
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 related.online-working.net)
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)
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
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.
