URLQuery
2 det.
Open reportPhishDestroy first recorded solarservicehouse.com on 2026-11-03. Stored VirusTotal flags: 13; the total engine count was not retained.
“SolarServiceHouse | Premium Solar Energy Shop”
Recorded source summary
PhishDestroy stores a record for solarservicehouse.com. Source observations are dated separately; missing checks do not establish safety.
A reviewed analysis is not available for this text revision. Consult the dated source records below.
2 det.
Open reportMalicious · engine verdict · score 97
SHA-256 d31a5c28d1d6a075d8727183304e201be3121779a4e5b94a49064e4ece1ab7b0
Observed: · Retrieved:
| Uuid | 01a1a003-d018-769c-bced-d45adb3f4b59 |
|---|---|
| Final url | https://solarservicehouse.com/ |
| Status | 200 |
| Redirected | https-only |
| Redirects | [
{
"to": "https://solarservicehouse.com/",
"from": "http://solarservicehouse.com/",
"status": 307
}
] |
| Ip | 103.29.181.100 |
| Contacted domains | [
"cdnjs.cloudflare.com",
"cdn.jsdelivr.net",
"fonts.gstatic.com",
"encrypted-tbn0.gstatic.com",
"fonts.googleapis.com"
] |
| Contacted IP addresses | [
"142.250.195.131",
"142.250.195.238",
"142.251.222.10",
"104.17.25.14",
"104.16.180.112",
"103.29.181.100"
] |
| Asns | [
"15169",
"13335",
"147303"
] |
| Countries | [
"US",
"BD"
] |
| Document hash | d31a5c28d1d6a075d8727183304e201be3121779a4e5b94a49064e4ece1ab7b0 |
| Globals | [
"uidEvent",
"bootstrap",
"openOrderModal",
"addToCart"
] |
| Cookies | [
"PHPSESSID"
] |
| Tls | {
"san": [
"*.solarservicehouse.com",
"solarservicehouse.com"
],
"cipher": "AES_128_GCM",
"issuer": "YR2",
"subject": "solarservicehouse.com",
"protocol": "TLS 1.3",
"valid_to": "2026-12-12T11:15:30Z",
"valid_from": "2026-09-13T11:15:31Z"
} |
| Domain age days | 238 |
| Apex age days | 238 |
| Tls age days | 50 |
| Tls valid days | 89 |
| Requests | 26 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 97,
"malicious": true
},
"overall": {
"score": 0,
"malicious": false
}
} |
| HTTP headers | {
"content-type": "text/html; charset=UTF-8"
} |
Separate stored monitor snapshot; does not replace the primary report record or establish current availability.
Scan report
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
Stored page, network and scanner observations, grouped by source and observation time.
| Mail configuration | {
"mx": [
"solarservicehouse.com"
],
"spf": "v=spf1 +a +mx +ip4:103.29.181.102 +ip4:103.29.181.98 +ip4:103.29.181.100 ~all",
"dkim": [
"default"
],
"dmarc": true,
"dkim_bits": 2048,
"spf_lookups": 2
} |
|---|---|
| Caa records | {
"domain": "solarservicehouse.com"
} |
| Protective DNS results | {
"resolvers": 12,
"blocked_by": [
"CloudFlare Family"
],
"blocked_count": 1
} |
| Page title and metadata | {
"title": "SolarServiceHouse | Premium Solar Energy Shop"
} |
| Forms and mixed content | {
"no_sri": [
"https://cdn.jsdelivr.net/npm/bootstrap@5.3.0/dist/js/bootstrap.bundle.min.js"
],
"third_party_scripts": 1
} |
| Status | {
"up": true,
"code": 200,
"timings": {
"dns": 517,
"tls": 211,
"wait": 218,
"connect": 209,
"download": 191
},
"response_ms": 1346
} |
| 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,
22,
25,
53,
80,
110,
143,
443,
587,
993,
995
]
} |
| Threats | {
"phishtank": true
} |
| Carbon | {
"bytes": 33082,
"co2_grams": 0.0012,
"cleaner_than": 46
} |
| Dns server | {
"ns": [
{
"ip": "103.174.152.157",
"host": "nsbd2.hostseba.com"
},
{
"ip": "104.234.134.152",
"host": "nsbd1.hostseba.com"
}
],
"zone": "solarservicehouse.com"
} |
| Location | {
"ip": "103.29.181.100",
"asn": "147303",
"org": "ColoCone",
"city": "Dhaka",
"country": "BD"
} |
| Ssl | {
"issuer": "Let's Encrypt / YR2",
"subject": "solarservicehouse.com"
} |
| DNS records | {
"A": [
"103.29.181.100"
],
"MX": [
"{\"exchange\": \"solarservicehouse.com\", \"priority\": 0}"
],
"NS": [
"nsbd1.hostseba.com",
"nsbd2.hostseba.com"
],
"SOA": "{\"nsname\": \"nsbd1.hostseba.com\", \"hostmaster\": \"hostseba\\\\.com.gmail.com\", \"serial\": 2026091301, \"refresh\": 3600, \"retry\": 1800, \"expire\": 1209600, \"minttl\": 86400}",
"TXT": [
"v=spf1 +a +mx +ip4:103.29.181.102 +ip4:103.29.181.98 +ip4:103.29.181.100 ~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": "103.29.181.100",
"family": 4
} |
| Redirects | {
"chain": [
"https://solarservicehouse.com"
]
} |
| Subdomains | {
"count": 1,
"subdomains": [
"delivery.solarservicehouse.com"
]
} |
| Page links | {
"internal_count": 15
} |
| Registration record | {
"registrar": "Unstoppable Domains Inc.",
"created": "2026-03-08T17:32:05Z",
"updated": "2026-03-13T10:00:21Z",
"expires": "2027-03-08T17:32:05Z",
"status": [
"clientDeleteProhibited https://icann.org/epp",
"clientTransferProhibited https://icann.org/epp"
],
"nameservers": [
"nsbd1.hostseba.com",
"nsbd2.hostseba.com"
]
} |
| HTTP headers | {
"headers": {
"content-type": "text/html; charset=UTF-8"
}
} |
PhishDestroy rates solarservicehouse.com as critical risk (100/100) from the recorded evidence; it was first recorded on 2026-11-03. Stored VirusTotal flags: 13; the total engine count was not retained. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.
This report does not record which wallet requests solarservicehouse.com makes. Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions there. A confirmed blockchain transaction cannot be reversed.
It depends on what you did. If you entered a password, change it, and also on every other site where you used the same password; turn on two-factor authentication where it is offered. If you paid or gave card or bank details, contact your bank or payment service through the contacts on your card or its official website. If you only connected a wallet, disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds. If you signed a token approval or permit, revoke it with a token-approval checker. If you shared a seed phrase or private key, treat the wallet as compromised and move the remaining funds to a new wallet with a new seed phrase. If you downloaded a file, do not open it and scan the device with security software. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority; a report does not guarantee that money is returned. Step-by-step help: emergency guide.
Checked, no match
Last checked
nsbd1.hostseba.comnsbd2.hostseba.comnsname: nsbd1.hostseba.comhostmaster: hostseba\.com.gmail.comserial: 2026091301refresh: 3600retry: 1800expire: 1209600minttl: 86400solarservicehouse.comLocation describes the IP network.
*.solarservicehouse.comsolarservicehouse.comSaved 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.
delivery.solarservicehouse.comDomain recordAn estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Network requests: 26 SHA-256 hashes: 26 URLScan scan:
Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-11-03 06:11 UTC.
Open this scan on URLScan 01a1a003-d018-769c-bced-d45adb3f4b59 ↗
| # | Network request | HTTP method · status | Type | Uncompressed size | Response body SHA-256 |
|---|
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Reachable
Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.
Recorded events: 7. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
PD-14C69C2545DFC0313D45 · Receipt 84342
solarservicehouse.com
View sourcePage captured
View sourceWe 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.
Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.
Download all records as JSON| ID | Stored data |
|---|
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
solarservicehouse.com PD-14C69C2545DFC0313D45 Recipient: abuse@visualsofts.net Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.
IC3 does not accept attachments. Keep original evidence for investigators. IC3 guidance
Federal tips line1-800-CALL-FBICurrent service: Report Fraud. England, Wales and Northern Ireland. Scotland: 101.
Contact centre0300 123 2040Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.
Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.
Forward scam emails and text messages to the National Cyber Security Centre, which takes down the malicious sites it finds.
Emailreport@phishing.gov.uk Text messages7726Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.
Forward phishing emails to the Anti-Phishing Working Group.
Emailreportphishing@apwg.orgNational Cyber Crime Reporting Portal. For financial fraud, also call the 1930 helpline straight away.
Helpline1930Select your country to get official cybercrime contacts, or create a complaint draft →.
If you made a payment, contact your bank or payment service through its official contacts as soon as possible. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned.
Scammers are criminals. Filing a report creates a legal record and helps protect others.
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 ↗
solarservicehouse.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.
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.