VirusTotal
4 / 89
SignalerInterpretation & limits
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
“Service Status”
Assessment based on the stored source evidence below. Review sources →
The sent-report ledger records the first outgoing report at .
The recorded recipient is complaint@gname.com.
The latest stored availability evidence still shows the domain reachable; 28 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.
com-a.sbs — Accessible · accès restreint (HTTP 403). Type d'arnaque : Impersonation. Résumé des preuves: VirusTotal 4/89 (alphaMountain.ai, Forcepoint ThreatSeeker, SOCRadar, Webroot); URLQuery 1 alert; 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 98/100. Bureau d’enregistrement: Gname.
L’analyse détaillée de PhishDestroy AI reste en anglais afin de préserver le relevé forensique original.
These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.
4 / 89
SignalerEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
1 threat-system alert
SignalerAlerts refer to the preserved scan. They do not describe the current state of the site.
2 external matches
DétailsA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
4 community references
SignalerCommunity publication references, not a vendor verdict or evidence of a common operator.
provider verdict: clean
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
rapport stocké
View stored capture ↗ SignalerA preserved page image documents what the collector received; a capture is not a safety verdict.
Analyse terminée
SignalerThis is the recorded automated analysis. Completion alone is not a safety verdict.
Checked; no threat flag recorded
SignalerA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DNS4EU | com-a.sbs |
malicious | Sinkholed |
Stored narrative · generated . Provider checks below retain their own observation dates.
Stored evidence for com-a.sbs: VirusTotal recorded 4 detections among 89 scanners on 2026-09-17. That ratio reproduces the stored check in its original units and is not converted into another measure. MetaMask and SEAL appear as named external blocklist observations for com-a.sbs. Each item in this report remains at the scope supplied by its dated source record.
VirusTotal records 4 detections among 89 scanners in the stored snapshot dated 2026-09-17. 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-17 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.
MetaMask and SEAL are recorded as named external blocklist observations for com-a.sbs in the snapshot dated 2026-09-17. The stored MetaMask and SEAL blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains com-a.sbs as a publisher record. That PhishDestroy record is counted separately from the MetaMask and SEAL 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.
The record first observed com-a.sbs on 2026-09-17. The MetaMask and SEAL blocklist snapshot is dated 2026-09-17 and remains a separate event in the stored timeline. The registration date is separately recorded as 2026-09-15. A URLScan reference was stored on 2026-09-17 as a dated artifact for review. 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.
The source stores 172.67.203.48 as the observed address in this record. The registration date for com-a.sbs is recorded as 2026-09-15. The SSL issuer is recorded as Let's Encrypt / YE2 in the snapshot dated 2026-09-17. The stored ASN observation records 13335 and Cloudflare, Inc. in this record. 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.
The com-a.sbs record states that VirusTotal recorded 4 detections among 89 scanners on 2026-09-17. MetaMask and SEAL remain named blocklist observations from the snapshot dated 2026-09-17. PhishDestroy remains a separate publisher catalogue entry in the stored record. The observed address field in this record contains 172.67.203.48. The supported conclusion is bounded to the exact stored observations for com-a.sbs. Any statement beyond those source values would require additional dated material.
Avoid submitting sensitive information to com-a.sbs during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain com-a.sbs as an exact indicator and preserve relevant DNS, proxy, and endpoint records. Compare later VirusTotal snapshots and MetaMask and SEAL 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 com-a.sbs. The stored record does not justify extending that rule to 172.67.203.48 or to other infrastructure records.
What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.
These checks have no retained result. This does not mean they passed or that a scan is running.
The linked repository preserves daily zone observations across seven ShortDot-operated TLDs, including registration volume and abuse-related indicators. This registry context is supporting background and is not an independent detection for the domain in this report.
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.
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.
La réputation Edge-IP n’est pas attribuée à ce domaine.
david.ns.cloudflare.comelinore.ns.cloudflare.comLocation describes the IP network.
4e1ace4b3c6a4d2cd4a28d980791bf44406334527cc3ca9fee2655bcc8e5e8bbSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of com-a.sbs · checked Sep 17, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
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.
cloudflareNote relative à la numérisation: cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial
Réponse du prestataire pendant l'examen: cloudflare_phishing_interstitial
172.67.203.48.Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Inconnu→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
blocked→Inconnu
probe_inconclusive
Inconnu→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
blocked→Inconnu
probe_inconclusive
Inconnu→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
blocked→Inconnu
probe_inconclusive
Inconnu→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
blocked→Inconnu
probe_inconclusive
Inconnu→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
blocked→Inconnu
probe_inconclusive
Inconnu→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
blocked→Inconnu
probe_inconclusive
Inconnu→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Inconnu
probe_inconclusive
Accessible→Indisponible
2→4
Accessible
13 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
PD-20260917-EA0692 Recipient: complaint@gname.com Registrar: Gname.com Pte. Ltd. (Singapore) Policy Violations: Illegal Activities section forbids phishing, fraud, fake sites, malware distribution; registrar investigates and may suspend or delete domain Applicable Laws: Computer Misuse Act 1993 §§3+, Penal Code §§415–420 (cheating), Online Criminal Harms Act (OCHA)
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.
Sélectionnez votre pays pour obtenir contacts officiels en matière de cybercriminalité ou créer un projet de plainte →.
Template-based draft · optional AI wording assistance requires separate consent
Analyse des menaces à l'aide de listes de blocage stockées, de WHOIS, de DNS et de preuves d'analyse publique
Scanner maintenantSignalez les domaines suspects à notre base de données des menaces — protégez la communauté
SignalerRapports de phishing récents et changements de disponibilité observés
SurveillerSurveillez les menaces en temps réel ou signalez cette alerte si vous pensez qu'il s'agit d'un faux positif