PhishDestroy identifies update365b.online as an active credential-phishing domain impersonating Microsoft 365 login pages to harvest corporate credentials. The domain was registered on March 27, 2026, and already exhibits risky behavior with 1 out of 95 VirusTotal security vendors flagging it as malicious. The site resolves to IP 145.79.213.135 via HOSTINGER operations, UAB and uses a Let’s Encrypt SSL certificate to appear legitimate.
This domain combines several red flags: a recent creation date only days old, low detection coverage with just 1/95 positives on VirusTotal, hosting through a consumer-grade provider, and an IP address with mixed reputation. No public blocklists or threat-intel platforms currently list the domain, suggesting the campaign may still be in early deployment. The Let’s Encrypt certificate provides a false sense of security and is commonly abused in credential phishing to avoid browser warnings.
Organizations and users should treat any login prompts linked to update365b.online as high-risk. Disable automatic forwarding from shortened URLs or email links that lead to this domain. Verify all login pages by manually navigating to the official Microsoft 365 portal rather than trusting embedded links. If credentials were entered, rotate passwords immediately, enable multi-factor authentication, and scan endpoints for follow-on compromise. Report indicators to PhishDestroy for blocking and threat analysis.
DOM Analysisanalyzed 2026年7月29日score 63/1001 brand signal
Submitted URLhttp://update365b.online/
ケース ID
ICANN OVERSIGHT
認定と RAA の背景
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 非アクティブreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation不明Probe Inconclusive20%2026-10-19 01:10:10 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-05-08 17:19:50 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-05-08 17:19:50 UTC → 2026-09-30 16:14:55 UTC · 3,478.92hmidpoint estimate ≈ 2026-07-20 04:47:22 UTC · precision very low · basis bounded
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.
使用技術 · 4 identified
L
LiteSpeed
Web servers
High-performance web server compatible with Apache configurations.
H
Hostinger
Google Analytics
Analytics
Web analytics service tracking website traffic and user behavior.
Google PageSpeed Insights — mobile performance audit of update365b.online· checked Mar 28, 2026
87
Needs Work
Performance
FCP
1s
First Contentful Paint
LCP
4.02s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
52ms
Total Blocking Time
SI
3.06s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Registration & observation details8
Availability observations
Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
3478.92
Estimate basis
Bounded by observations
Estimate precision
very_low
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Check for cloaking
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
No cloaking flag in this check
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='update365b.online', port=80): Max retries exceeded with url: / (Caused by NewConnectionErr
update365b.online
保存済みの結果
到達不能
Stored observation history10
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
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.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
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.
