VirusTotal
4 / 92 engine detections
Open reportdashadom.com is a blocklisted domain detected by PhishDestroy on 2026-10-20. Risk: critical (78/100). Registrar: Arsys Internet, S.L. d…. Status: Last known active. Hosting: Nicalia Internet, S.L.U. PhishDestroy sent 1 abuse report. VirusTotal: 4/92 engines flag it. Do not enter credentials or connect a wallet.
“DASHADOM.COM - Sales Home”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@nicline.com.
The latest stored availability evidence still shows the domain reachable; 2 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.
4 / 92 engine detections
Open report3 det.
Open reportno community references
Open reportprovider verdict: clean
Open reportNo threat flag
Open reportNo malicious flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
PhishDestroy has added dashadom.com to its internal blocklist as a suspicious domain. The site was first observed by PhishDestroy on 2026-10-20. No page title was recorded at the time of observation.
Because no particular scam type was identified, the listing reflects general suspicion based on external detections rather than observed malicious behavior. Without a known page title or content, we cannot describe a concrete phishing, wallet‑draining, or fake‑exchange flow. In general, domains flagged by multiple security engines may be used for credential harvesting, fraudulent services, or malware distribution, but this cannot be confirmed for dashadom.com.
VirusTotal scanned dashadom.com on 2026-10-20 and reported 4 detections out of 92 engines, with alerts from alphaMountain.ai, CRDF, SOCRadar and Webroot. Google Safe Browsing checked the domain on 2026-10-20 and did not flag it. No external blocklists listed the domain as of 2026-10-20, while PhishDestroy’s internal list marked it as suspicious on the same day. OTX recorded zero pulses for dashadom.com on 2026-10-20.
The domain dashadom.com was registered on 2011-12-23 through Arsys Internet, S.L. dba NICLINE.COM. The recorded IP address associated with the domain is 92.60.33.50. No additional network or CDN details are available.
Visitors should avoid entering any personal or financial information on dashadom.com. If credentials were entered, change the associated passwords and monitor accounts for unauthorized activity. Security teams should add dashadom.com to their block or monitoring lists and review any logs for connections to 92.60.33.50.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 01a159b7-1325-7074-b33c-953d34fad301 |
|---|---|
| Final url | https://dashadom.com/auth/ |
| Status | 200 |
| Redirected | same-domain |
| Redirects | [
{
"to": "https://dashadom.com/auth",
"from": "http://dashadom.com/auth",
"status": 307
},
{
"to": "https://dashadom.com/auth/",
"from": "https://dashadom.com/auth",
"status": 301
}
] |
| Ip | 92.60.33.50 |
| Ptr | ibersoft.es |
| Contacted domains | [
"wolfish.site",
"ajax.googleapis.com",
"www.google.com",
"wiki.com"
] |
| Contacted IP addresses | [
"142.251.155.119",
"189.12.234.88",
"192.178.155.95",
"92.60.33.50"
] |
| Asns | [
"15169",
"399114",
"208769"
] |
| Countries | [
"US",
"ES"
] |
| Document hash | 8d0a44d2a2848df9a1e1199ba6e471fc5d45a27c23f9c63e038001d97d5c14c8 |
| Globals | [
"$",
"jQuery",
"Ls",
"gpp",
"Init",
"aiF",
"cStart",
"redir",
"cfg",
"root",
"redirect",
"wmsg",
"lg"
] |
| Storage keys | [
"pp"
] |
| Tls | {
"san": [
"*.dashadom.com",
"dashadom.com"
],
"cipher": "AES_128_GCM",
"issuer": "YR2",
"subject": "*.dashadom.com",
"protocol": "TLS 1.3",
"valid_to": "2027-01-18T06:12:41Z",
"valid_from": "2026-10-20T06:12:42Z"
} |
| Domain age days | 3624 |
| Apex age days | 3624 |
| Tls age days | 0 |
| Tls valid days | 89 |
| Requests | 9 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 38,
"malicious": true
},
"overall": {
"score": 0,
"malicious": false
}
} |
| HTTP headers | {
"server": "LiteSpeed",
"content-type": "text/html"
} |
Observed: · Retrieved:
| Uuid | 3a7b3087-3734-4eb2-8ab8-b5e971ee0775 |
|---|---|
| Final url | https://dashadom.com/ |
| Status | 200 |
| History | [
{
"url": "https://dashadom.com/",
"status": 200
}
] |
| DOM structure hash | e0d7e88d354c829230ab694e8acab2b1266e59e32c43b385e585255599bfee7e |
| Document hash | 3b6ae1a6b24f3666f0ef09d4631d30c8bdd7ed0aa4ffd0ed549a2f67d74fa180 |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "dashadom.com",
"type": "A",
"value": "92.60.33.50"
}
] |
| Dnssec valid | false |
| Ip | 92.60.33.50 |
| Registration record | {
"registrar": "Arsys Internet, S.L. dba NICLINE.COM",
"created": "2011-12-23T17:20:10Z",
"updated": "2025-12-24T08:25:51Z",
"expires": "2026-12-23T17:20:10Z",
"nameservers": [
"ns1.ibersoft.es",
"ns2.ibersoft.es"
]
} |
Observed: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 52,
"malicious": 3,
"suspicious": 2,
"undetected": 35
} |
|---|---|
| Vendor labels | {
"CRDF": "malicious",
"Webroot": "malicious",
"SOCRadar": "suspicious",
"Gridinsoft": "phishing",
"alphaMountain.ai": "suspicious"
} |
| Reputation | 0 |
| Created | 2011-12-23T00:00:00Z |
| Updated | 2025-12-24T00:00:00Z |
| First seen | 2025-08-19T04:32:06Z |
| DNS records | [
{
"ttl": 3158,
"type": "SOA",
"rname": "comercial.ibersoft.es",
"value": "ns1.ibersoft.es"
},
{
"ttl": 3600,
"type": "A",
"value": "92.60.33.50"
},
{
"ttl": 3600,
"type": "NS",
"value": "ns3.host-fusion.com"
},
{
"ttl": 3600,
"type": "NS",
"value": "ns1.ibersoft.es"
},
{
"ttl": 14400,
"type": "TXT",
"value": "google-site-verification=4UhuGazUz3dtoi8S7V4qSOXuO9qgO60GJwv9VYGpUa0"
},
{
"ttl": 14400,
"type": "MX",
"value": "SMTP.GOOGLE.com",
"priority": 1
},
{
"ttl": 3600,
"type": "NS",
"value": "ns4.host-fusion.com"
},
{
"ttl": 14400,
"type": "TXT",
"value": "v=spf1 ip4:92.60.33.50 include:_spf.google.com ~all"
},
{
"ttl": 3600,
"type": "NS",
"value": "ns2.ibersoft.es"
}
] |
| Dns at | 2026-10-20T16:35:56Z |
| Jarm | 29d29d00029d29d00042d43d00041d598ac0c1012db967bb1ad0ff2491b3ae |
| Certificate | {
"san": [
"*.dashadom.com",
"dashadom.com"
],
"issuer": "Let's Encrypt / YR2",
"serial": "6b8452882f4958011f414c07e9d85f3d145",
"sha256": "2cd72430e101425c3e215e4850631b6373bfcb44c19e15775443b7767c743030",
"subject": "*.dashadom.com",
"valid_to": "2027-01-18T06:12:41Z",
"valid_from": "2026-10-20T06:12:42Z"
} |
| Mail configuration | {
"mx": [
"SMTP.GOOGLE.com"
],
"spf": "v=spf1 ip4:92.60.33.50 include:_spf.google.com ~all",
"dmarc": true,
"providers": [
"Google Workspace"
],
"spf_lookups": 1
} |
|---|---|
| Caa records | {
"domain": "dashadom.com"
} |
| Protective DNS results | {
"resolvers": 12,
"blocked_count": 0
} |
| Web archive observations | {
"last": "2026-10-20T13:21:33Z",
"first": "2012-05-13T22:33:11Z",
"changes": 7,
"days_archived": 24,
"scans_per_day": 0,
"avg_page_bytes": 1162
} |
| Page title and metadata | {
"title": "DASHADOM.COM - Sales Home"
} |
| Trackers | {
"requests": 3
} |
| Forms and mixed content | {
"third_party_scripts": 0
} |
| Status | {
"up": true,
"code": 200,
"timings": {
"dns": 58,
"tls": 38,
"wait": 35,
"connect": 33,
"download": 0
},
"response_ms": 164
} |
| TLS connection | {
"alpn": "h2",
"cipher": "TLS_AES_256_GCM_SHA384",
"protocol": "TLSv1.3",
"versions": [
"TLSv1.2",
"TLSv1.3"
],
"authorized": true,
"forward_secrecy": true
} |
| Ports | {
"open": [
21,
25,
53,
80,
110,
143,
443,
587,
993,
995,
3306
]
} |
| Carbon | {
"bytes": 1302,
"co2_grams": 0,
"cleaner_than": 95
} |
| Dns server | {
"ns": [
{
"ip": "95.179.232.48",
"host": "ns2.ibersoft.es"
},
{
"ip": "92.60.33.91",
"host": "ns3.host-fusion.com"
},
{
"ip": "92.60.33.88",
"host": "ns1.ibersoft.es"
},
{
"ip": "45.77.163.113",
"host": "ns4.host-fusion.com"
}
],
"zone": "dashadom.com"
} |
| Location | {
"ip": "92.60.33.50",
"asn": "208769",
"org": "Nicalia Internet, S.L.U",
"city": "Canet de Mar",
"country": "ES"
} |
| Ssl | {
"issuer": "Let's Encrypt / YR2",
"subject": "*.dashadom.com"
} |
| DNS records | {
"A": [
"92.60.33.50"
],
"MX": [
"{\"exchange\": \"SMTP.GOOGLE.com\", \"priority\": 1}"
],
"NS": [
"ns1.ibersoft.es",
"ns4.host-fusion.com",
"ns2.ibersoft.es",
"ns3.host-fusion.com"
],
"SOA": "{\"nsname\": \"ns1.ibersoft.es\", \"hostmaster\": \"comercial.ibersoft.es\", \"serial\": 2026102001, \"refresh\": 3600, \"retry\": 1800, \"expire\": 1209600, \"minttl\": 86400}",
"TXT": [
"google-site-verification=4UhuGazUz3dtoi8S7V4qSOXuO9qgO60GJwv9VYGpUa0",
"v=spf1 ip4:92.60.33.50 include:_spf.google.com ~all"
]
} |
| Dnssec | {
"ds": false,
"rrsig": false,
"dnskey": false
} |
| Hsts | {
"message": "Site does not serve any HSTS headers."
} |
| HTTP security policies | {
"xFrameOptions": false,
"referrerPolicy": false,
"xXSSProtection": false,
"permissionsPolicy": false,
"xContentTypeOptions": false,
"contentSecurityPolicy": false,
"strictTransportPolicy": false,
"crossOriginOpenerPolicy": false,
"crossOriginEmbedderPolicy": false,
"crossOriginResourcePolicy": false
} |
| Get ip | {
"ip": "92.60.33.50",
"family": 4
} |
| Redirects | {
"chain": [
"https://dashadom.com"
]
} |
| Tech stack | {
"technologies": [
"LiteSpeed",
"HTTP/3"
]
} |
| Page links | {
"external": [
"https://youtu.be/G8OYl8Lnilw"
],
"external_count": 1,
"internal_count": 5
} |
| Registration record | {
"registrar": "Arsys Internet, S.L. dba NICLINE.COM",
"created": "2011-12-23T17:20:10Z",
"updated": "2025-12-24T08:25:51Z",
"expires": "2026-12-23T17:20:10Z",
"status": [
"ok https://icann.org/epp"
],
"nameservers": [
"ns1.ibersoft.es",
"ns2.ibersoft.es"
]
} |
| HTTP headers | {
"headers": {
"server": "LiteSpeed",
"content-type": "text/html"
}
} |
No. PhishDestroy classifies dashadom.com as a blocklisted domain (risk: critical, 78/100); it was first detected on 2026-10-20. VirusTotal: 4/92 engines flag it. Treat the site as unsafe.
No. Do not connect a wallet, sign messages or approve tokens on dashadom.com. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
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.
ns1.ibersoft.esns2.ibersoft.esns3.host-fusion.comns4.host-fusion.comSMTP.GOOGLE.compriority 1Location describes the IP network.
2cd72430e101425c3e215e4850631b6373bfcb44c19e15775443b7767c743030Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
autodiscover.dashadom.comDomain recordcpanel.dashadom.comDomain recordcpcalendars.dashadom.comDomain recordcpcontacts.dashadom.comDomain recordmail.dashadom.comDomain recordwebdisk.dashadom.comDomain recordwebmail.dashadom.comDomain recordwww.dashadom.comDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of dashadom.com · checked Oct 20, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://dashadom.com/authhttp://dashadom.com/auth/Content-Type: text/htmlContent-Encoding: gzipServer: LiteSpeedbytesKeep-Alivegzip984text/htmlTue, 20 Oct 2026 13:23:29 GMTtimeout=5, max=100Mon, 28 Sep 2026 15:14:40 GMTLiteSpeedAccept-EncodingValues retained by the collector; long values may be shortened during collection.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→live_content
content_served
Unknown→live_content
content_served
No threat flag
View sourcePD-20261020-93CC86
Page captured
View source4/92 engine detections
View sourcedashadom.com
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
dashadom.com
PD-20261020-93CC86 Recipient: abuse@nicline.com If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
dashadom.com)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
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.