Aller au rapport de sécurité
Sécurité des domaines et renseignements sur les menaces
theodore3.com favicon

theodore3.com

“Microsoft | Login”

Bureau d’enregistrement
TUCOWS.COM, CO
Resolved IP
162.241.24.83
Registered
22/06/2007
Verdict de menace Critique
Disponibilité Dernier actif connu Dernière observation d'accessibilité stockée Observé
Source: HTTP probe
Détections VirusTotal : 16/92 Usurpation de l'identité de la marque : Microsoft
27/09/2026 Microsoft 1 Report Sent
API
Ce domaine a été signalé comme malveillant
Moteurs de sécurité signalant une détection : 16. Faites preuve d’une extrême prudence – ne saisissez pas d’informations d’identification ou d’informations personnelles.
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@bluehost.com. The latest stored availability evidence still shows the domain reachable; 16 days 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
16 days
Reports sent
1
Latest case ID
PD-20260927-30D745
Current status
HTTP 301 at latest stored check
Résumé du rapport

theodore3.com — Dernier actif connu (HTTP 301). Usurpation de l'identité de la marque : Microsoft; Type d'arnaque : Credential Phishing. Résumé des preuves: VirusTotal 16/92 (Abusix, alphaMountain.ai, BitDefender, CRDF, ESET); URLQuery 5 det.; URLScan malicious verdict; PhishDestroy score 100/100. Bureau d’enregistrement: TUCOWS.COM, CO.

L’analyse détaillée de PhishDestroy AI reste en anglais afin de préserver le relevé forensique original.

VirusTotal
VirusTotal
16 det.
URLQuery
URLQuery
5 det.
URLScan
URLScan
Certificat TLS
Expiré ou non vérifié 22d
Âge
19.3 yr
Statut observé
Dernier actif connu 301
PhishDestroy
DestroyList
Répertorié
Reports Sent
1

Source evidence

7 sources

VirusTotal

16 / 92

Signaler

URLScan verdict

malicious

Signaler

OTX

no community references

Signaler

CF Radar

provider verdict: clean

Signaler

URLScan capture

rapport stocké

Stored URLScan capture preview
Signaler

Google Safe Browsing

Checked; no threat flag recorded

Signaler

Résumé des preuves

Critique
VirusTotal
16/92
URLScan
Stored capture

Assessment

Stored evidence for theodore3.com: VirusTotal recorded 13 detections among 91 scanners on 2026-09-27. That ratio reproduces the stored check in its original units and is not converted into another measure. OpenPhish and Phishunt appear as named external blocklist observations for theodore3.com. Each item in this report remains at the scope supplied by its dated source record.

Detection Evidence

VirusTotal records 13 detections among 91 scanners in the stored snapshot dated 2026-09-27. The numerator describes scanners that produced detections, while the denominator describes scanners included in that check. The reverse order would materially alter the stored result. The VirusTotal snapshot dated 2026-09-27 supplies no common rationale covering the included scanners, and this report adds none. A later VirusTotal snapshot may contain different values, so any comparison should preserve the exact ratio and date of each snapshot.

Source Context

OpenPhish and Phishunt are recorded as named external blocklist observations for theodore3.com in the snapshot dated 2026-09-27. The stored OpenPhish and Phishunt blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains theodore3.com as a publisher record. That PhishDestroy record is counted separately from the OpenPhish and Phishunt external blocklist observations. This separation keeps the origin of every entry visible and prevents a single stored item from being counted again under another source label.

Reachability and Timeline

The record first observed theodore3.com on 2026-09-27. The OpenPhish and Phishunt blocklist snapshot is dated 2026-09-27 and remains a separate event in the stored timeline. The registration date is separately recorded as 2007-06-22. Each timestamp qualifies only the adjacent observation in this timeline. Later collection results should be compared with these dated values without replacing the earlier snapshot.

Registration and Infrastructure

For theodore3.com, the registrar field records Tucows Domains Inc.; this is kept as an exact source value. The source stores 162.241.24.83 as the observed address in this record. The registration date for theodore3.com is recorded as 2007-06-22. These fields preserve registration, network, and certificate context stored in this record. The report preserves each label and number as a separate source value instead of combining them into an invented aggregate. Keeping the fields separate leaves every infrastructure value traceable to the record that supplied it.

Conclusion

The theodore3.com record states that VirusTotal recorded 13 detections among 91 scanners on 2026-09-27. OpenPhish and Phishunt remain named blocklist observations from the snapshot dated 2026-09-27. PhishDestroy remains a separate publisher catalogue entry in the stored record. For theodore3.com, the registrar field records Tucows Domains Inc.; this remains separate from the other source fields. The observed address field in this record contains 162.241.24.83. The supported conclusion is bounded to the exact stored observations for theodore3.com. Any statement beyond those source values would require additional dated material.

Recommended Actions

Avoid submitting sensitive information to theodore3.com during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain theodore3.com as an exact indicator and preserve relevant DNS, proxy, and endpoint records. Compare later VirusTotal snapshots and OpenPhish and Phishunt blocklist records with the dated values above instead of replacing them. Keep each later observation with its source date so changes remain visible during follow-up review. If a defensive rule is needed, keep its scope to theodore3.com. The stored record does not justify extending that rule to 162.241.24.83 or to other infrastructure records.

Analyse de la détection et de l'évasion

Vérification du cloaking et de la répartition du trafic

Pas encore numérisé Aucune différence entre les robots d'indexation et les navigateurs n'a encore été constatée

Enregistrement des observations « crawler contre navigateur » pour cet hôte, ainsi qu'une vérification en temps réel des empreintes numériques pour les systèmes de répartition du trafic de type Keitaro.

Indicateur de camouflage enregistré
Pas encore numérisé
Dernier scan de camouflage
En-tête du serveur détecté par le scanner
nginx/1.29.8

Note relative à la numérisation: redirect: raw=redirect_301; http=301; via=https_proxy; location=https://www.theodore3.com/; server=nginx/1.29.8

Vérification en direct des empreintes digitales d'TDS
Sept empreintes Keitaro ainsi qu’une comparaison entre robot d’indexation et navigateur, générées par le scanner PhishDestroy lorsque ce panneau est ouvert.
En attente

Capture enregistrée · 3 captures

Domain details

Domaine
URLScan Verdict Malveillant score 100 Phishing brand: Microsoft report ↗
Réputation de l’IP abuse score 0/100 0 reports checked 27/09/2026
Bureau d’enregistrement TUCOWS.COM, CO US(US)
EnregistrementCréé 22/06/2007 — Expires 22/06/2027
Statut HTTP301 Moved Permanently
Détails techniquesProvenance & timestamps
Première détection27/09/2026
DOM Analysisanalyzed 09/10/2026score 88/1001 brand signal
Submitted URLhttp://theodore3.com/the-cover-up/wp-content/upgrade/Microsoft.html
Favicon Hash
ID du dossier
Titre de la page
Microsoft | Login
Impersonates
Microsoft
Certificat TLS
Certificate hostname mismatch · Émis par Let's Encrypt / YR2 · stored validity ends in 22 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
162.241.24.83
Network ASN
AS31898
Organization
ORACLE-BMC-31898 - Oracle Corporation, US
Observed location
Phoenix, US
Server header
nginx/1.29.8

Serveurs de noms 2

  • ns1.bluehost.com
  • ns2.bluehost.com

Mail routing 1 MX record

  • theodore3.compriority 0

Location describes the IP network.

Certificat TLS

Issuer
Let's Encrypt / YR2
Valid from
2026-08-07 06:46:08
Valid until
2026-11-05 06:46:07
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-09 13:03:38 UTC
Collection source
PhishDestroy collector
Certificate fingerprint80aa8ca14bc0808282b1d559e68b5e3d00111bda349463f33119073353a0d833
Certificate names · 9 SANs
  • autoconfig.theodore3.com
  • autodiscover.theodore3.com
  • cpanel.theodore3.com
  • cpcalendars.theodore3.com
  • cpcontacts.theodore3.com
  • mail.theodore3.com
  • webdisk.theodore3.com
  • webmail.theodore3.com
  • www.theodore3.com

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

viewdns.info · 162.241.24.83rapiddns.io

Latest Classified Outcome 2026-10-13 10:09:37 UTC

Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-10-13 10:09:37 UTC
RDAP registration Inconnu
Observed timeline last reachable: 2026-10-13 10:09:37 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 · 11 identified
Detected via Cloudflare Radar · Wappalyzer engine
Signaler ce domaine Envoyez des éléments de preuve et contribuez à protéger les autres

Analyse VirusTotal

16 / Les fournisseurs de sécurité 92 ont signalé ce domaine
View on VT
Last analyzed Previous stored snapshot: 13 detections
Abusix
alphaMountain.ai
BitDefender
CRDF
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Lionic
Seclookup
SOCRadar
Sophos
URLQuery
VIPRE
Webroot

Preuves archivées

Wayback Machine Snapshot
Un instantané historique est disponible pour l’examen des preuves
View Archive
Analyse des performances du site

Google PageSpeed Insights — mobile performance audit of theodore3.com · checked Sep 27, 2026

63
Needs Work
Performance
FCP
3.34s
First Contentful Paint
LCP
12.35s
Largest Contentful Paint
CLS
0.004
Cumulative Layout Shift
TBT
90ms
Total Blocking Time
SI
5.87s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor

Forensic History & Detection Timeline

ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
  1. Status Check 2026-09-27 03:17:12 UTC
    Telemetry event observed.
  2. Threat First Observed 2026-09-27 03:16:51 UTC
    Domain ingestion complete. Initial state is marked as alive pointing to IP 162.241.24.83.

Processus de réponse aux menaces Pipeline

Découverte
Analysis
Notifications
Monitoring

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

Menace détectée
theodore3.com détectés et mis en file d'attente en vue d'une analyse complète
27/09/2026
URLScan.io Capture
Enregistré URLScan report with capture artifacts
27/09/2026
URLScan Verdict
URLScan returned a malicious verdict · score 100
27/09/2026
Cloudflare Radar Report
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
Web Archive
Preserved in Wayback Machine — historical evidence archived
29/09/2026
VirusTotal
16/92 recorded on VirusTotal
07/10/2026
Brand Impersonation
Impersonation of Microsoft
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
27/09/2026
Technical Analysis Recorded
Le rapport contient des résultats de technologie ou d’analyse médico-légale stockés.
13/10/2026
Sent Report Recorded
Stored outgoing record associated with registrar TUCOWS.COM, CO., 2 abuse contacts
abuse@bluehost.comdomainabuse@tucows.com
27/09/2026
DestroyList publié
27/09/2026
Monitoring Continues
Le domaine reste accessible ou restreint en accès ; des contrôles futurs pourraient mettre à jour cette observation.
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.

Données factuelles et rapports externes

Instantané des preuves transmises
Sent: Ledger records: 1 Case ID: PD-20260927-30D745 Recipient: abuse@bluehost.com
Page title stored with report: Microsoft | Login
URLScan evidence VirusTotal evidence URLQuery evidence Screenshot 25.2 KB
PDF notice generated Notice text archived (653 chars)
Abuse notice text as sent to the provider
Policy Violations:
Illegal Activities: Active phishing operation targeting victims
Fraud & Deception: Impersonation of legitimate services
Identity Theft: Collection of credentials under false pretenses
Applicable Laws (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.
Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
Référencement naturel et nom de domaine
Analyse approfondie

Ce site vous a-t-il affecté ?

5 evidence signal groups linked 1 reports recorded Dernier actif connu
If credentials were compromised, report immediately. Do not engage with recovery scammers.

Si vous avez saisi des informations d'identification de compte, des informations personnelles ou de paiement, ou téléchargé un fichier à partir de ce domaine, agissez immédiatement. Vous trouverez ci-dessous des ressources pour vous aider à signaler l'incident et à vous protéger.

Europol
Trouvez le canal de signalement officiel pour votre pays de l'UE
National police directory
Méfiez-vous des escrocs qui prétendent vous aider à récupérer vos biens ! Les criminels peuvent recontacter leurs victimes tout en se faisant passer pour des enquêteurs, des avocats ou des agents de recouvrement. Ne payez pas de frais initiaux et ne partagez pas vos informations d'identification. En savoir plus sur la fraude liée aux aides à la reprise →

Signalez-le à vos autorités locales

Sélectionnez votre pays pour obtenir contacts officiels en matière de cybercriminalité ou créer un projet de plainte →.

Annuaire de 97 pays

Template-based draft · optional AI wording assistance requires separate consent

Brouillon assisté par l'IA : les détails de l'incident sont traités par le fournisseur d'IA · Examinez-le et soumettez-le vous-même

Vérifier n'importe quel domaine

Analyse des menaces à l'aide de listes de blocage stockées, de WHOIS, de DNS et de preuves d'analyse publique

Scanner maintenant

Signaler une tentative d'hameçonnage

Signalez les domaines suspects à notre base de données des menaces — protégez la communauté

Signaler

Flux d'alertes en temps réel

Rapports de phishing récents et changements de disponibilité observés

Surveiller

Restez informés, restez en sécurité

Surveillez les menaces en temps réel ou signalez cette alerte si vous pensez qu'il s'agit d'un faux positif

Flux d'alertes en temps réel Contester cette annonce
HTML · IFRAME

Intégrer ce rapport

Partagez ces informations sur les menaces sur votre site web ou votre blog

embed.html
<iframe
  src="https://phishdestroy.io/fr/embed/domain/theodore3.com"
  title="PhishDestroy threat report for theodore3.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>