Skip to security report
Domain security report
peihsi.com favicon

peihsi.com

“PEIHSI 沛曦|Dyson 維修・家電深層清潔|內湖・三重門市”

Threat verdict
Assessment sources

Assessment based on the stored source evidence below. Review sources →

Availability Last known active Latest stored reachability observation Observed · HTTP probe
Stored PhishDestroy threat listing Automated brand label: Facebook Young domain: 4 days old
OTX: 4 refs Oct 16, 2026 Facebook 1 Report Sent
API
Registrar
Gransy, s.r.o
Resolved IP
52.37.165.222
Registered
Oct 11, 2026
2 sources
In this reportGet help
⚠️
Suspicious Domain — Listed on PhishDestroy
Stored PhishDestroy threat listing. VirusTotal analysis stored; no vendor detections were recorded at check time. Exercise extreme caution — do not enter credentials or personal information.

Additional indicators at a glance

OTX references
URLScan
URLScan
TLS Certificate
Within stored validity dates
Let's Encrypt / YE2 · Hostname coverage not recorded
Age
4d Brand New!
Observed status
Last known active 200
PhishDestroy
DestroyList
Listed
Reports Sent
1

Source evidence

7 · sources

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.

VirusTotal

checked — no detections recorded

Report
Interpretation & limits

Engine detections from this stored analysis. Vendors and collection times may differ from other sources.

URLQuery

Report stored; detailed verdict not recorded

Observation time not recorded
Report
Interpretation & limits

Alerts refer to the preserved scan. They do not describe the current state of the site.

OTX

4 community references

Report
Interpretation & limits

Community publication references, not a vendor verdict or evidence of a common operator.

CF Radar

provider verdict: clean

Observation time not recorded
Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

URLScan capture

stored report

View stored capture ↗
Report
Interpretation & limits

A preserved page image documents what the collector received; a capture is not a safety verdict.

Google Safe Browsing

Checked; no threat flag recorded

Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Public blocklists

0 external matches

Details
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Evidence Summary

Critical
OTX
4 community refs
URLScan
Stored capture

AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.

Assessment

peihsi.com was observed with a PhishDestroy internal listing on 2026-10-16, documenting its inclusion in the publisher's catalogue for review. The domain also received a PageSpeed performance score of 56 on the same date, offering a technical metric for its web infrastructure.

Recorded Evidence

VirusTotal recorded a scan of peihsi.com on 2026-10-15, reporting 0 detections from 92 total scanners. OTX referenced the domain with 4 pulses on 2026-10-16. The domain was registered with Gransy, s.r.o. on 2026-10-11, and its SSL certificate was issued by Let's Encrypt / YE2, scanned on 2026-10-16. PageSpeed measured a performance score of 56 on 2026-10-16, and PhishDestroy listed the domain internally for review on the same date.

Interpretation

PhishDestroy provides a catalogue listing for peihsi.com, which documents its inclusion for internal monitoring purposes. VirusTotal offers a quantitative scan result, measuring detections across numerous scanners, while OTX records the domain's presence in its intelligence pulses. These sources together give a technical context for the domain's recorded status within security and performance records.

Recommended Actions

For peihsi.com, retain the VirusTotal scan results and OTX pulse references for ongoing comparison with future evidence. Preserve the PhishDestroy internal listing as a baseline for monitoring any subsequent changes. Use the PageSpeed performance score to inform future technical reviews and compare infrastructure metrics over time.

Data coverage & collection

21 · datasets with records / 10 · not recorded

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.

Recorded dataPartial recordUTC
VirusTotal
0 / 92 · engine detections
URLScan analysis
Capture retained; no provider verdictCollection time not recorded
URLQuery
Stored source recordCollection time not recorded
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
4 · community references
External blocklists
0 · external matches
Cloudflare Radar
cleanCollection time not recorded
Domain registration
Gransy, s.r.o.Collection time not recorded
Network & DNS
52.37.165.222 · 4 · nameserversCollection time not recorded
TLS certificate
Let's Encrypt / YE2
Page captures
2 · retained captures
HTML archives
1 · retained responses
Page analysis
2 · automated brand labels
Detection & evasion
Stored browser and crawler comparison
Site configuration files
robots.txt · sitemap.xml · security.txt
PageSpeed performance
56/100 · mobile performance
Response records
1 · outgoing report records
Recorded subdomains
1 · retained hostnamesCollection time not recorded
Availability history
2 · stored state changes
Source observation history
1 · stored source events
IP reputation
Network-level observations
Not recorded in this report 10

These checks have no retained result. This does not mean they passed or that a scan is running.

  • PhishStats
  • DNS security filters
  • Gridinsoft
  • Scamadviser
  • Spamhaus DBL
  • Observed indicators
  • Lookalike relationships
  • Community reports
  • Chainabuse records
  • Wayback archive
Download the dated observations and supporting metadata.

Blocklist records

0 · external source matches

Public Blocklist Status

Domain, network & archive

Gransy, s.r.o. · 52.37.165.222 · DNS, TLS and retained responses

Domain details

Domain
IP Reputation abuse score 0/100 0 reports checked Oct 16, 2026
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar Gransy, s.r.o
Abuse contactabuse@regtons.com
RegistrationCreated Oct 11, 2026 (4d · Brand New!) — Expires Oct 11, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 16, 2026
DOM Analysisanalyzed Oct 16, 2026score 83/1002 brand signals
Submitted URLhttp://peihsi.com/
Favicon Hash
Case ID

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
52.37.165.222
Network ASN
AS16509
Organization
Amazon.com, Inc.
Observed location
Boardman, US
Nameservers 4
  • readdy.earth.orderbox-dns.com
  • readdy.mars.orderbox-dns.com
  • readdy.mercury.orderbox-dns.com
  • readdy.venus.orderbox-dns.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-10-12 00:38:14
Valid until
2027-01-10 00:38:13
Hostname coverage
Hostname coverage not recorded
Validity
Within stored validity dates
Collection time
2026-10-16 10:02:07 UTC
Collection source
PhishDestroy collector
Certificate fingerprint74768b639e74712e30c3669492db4f562266e58f41bfe47f4cd36ba34de1a10c

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

Latest Classified Outcome 2026-10-16 11:01:16 UTC

Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Stale Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-10-16 11:01:16 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-16 11:01:16 UTC last content: 2026-10-16 11:01:16 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.
Recorded subdomains1

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • www.peihsi.comDomain record

The original observation time is not recorded for these hostnames.

Report This Domain Submit evidence & help protect others
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of peihsi.com · checked Oct 16, 2026

56
Needs Work
Performance
FCP
10.22s
First Contentful Paint
LCP
12.62s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
10.22s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://peihsi.com/
Final URL: https://peihsi.com/
PEIHSI 沛曦|Dyson 維修・家電深層清潔|內湖・三重門市
PEIHSI 沛曦提供 Dyson 吸塵器、吹風機、循環扇、掃地機器人維修與清潔,以及各品牌空氣清淨機、除濕機深層清潔。內湖、三重門市,歡迎先提供品牌型號與機況諮詢。
Response
HTTP 200
HTML body
3.1 KB
Compressed
1.4 KB
Links
0 internal · 0 external
Selected response headers
Cache-Control: public, max-age=0, must-revalidate
Content-Encoding: gzip
Content-Type: text/html; charset=utf-8
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Open Graph title: PEIHSI 沛曦|Dyson 維修・家電深層清潔
Open Graph description: 內湖、三重門市,依機器需求提供維修與清潔保養服務。
Saved response-header values · 7
Cache-Control
public, max-age=0, must-revalidate
Content-Encoding
gzip
Content-Length
1553
Content-Type
text/html; charset=utf-8
Date
Fri, 16 Oct 2026 09:43:09 GMT
Etag
"1ae6be3089617d9ec1bdbe61f61436a8"
Vary
Accept-Encoding

Values retained by the collector; long values may be shortened during collection.

Crawler & disclosure files

Site configuration evidence

3 · file checks

Stored file checks, including unavailable and invalid responses. Retained contents and paths appear where available.

robots.txt

Unverified (legacy)
/robots.txt
HTTP response
301
Observed at
2026-10-16 09:43:10 UTC
Source
legacy scan archive

A legacy response is stored, but it does not establish whether the file exists.

Sitemap

Unverified (legacy)
/sitemap.xml
HTTP response
301
Observed at
2026-10-16 09:43:10 UTC
Source
legacy scan archive

A legacy response is stored, but it does not establish whether the file exists.

security.txt

Unverified (legacy)
/.well-known/security.txt
HTTP response
301
Observed at
2026-10-16 09:43:10 UTC
Source
legacy scan archive

A legacy response is stored, but it does not establish whether the file exists.

Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Detection & evasion checks

Stored browser and crawler observations

Detection-evasion analysis

Cloaking and traffic-distribution check

Not yet scanned No crawler-versus-browser difference has been recorded yet

Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.

Stored cloaking flag
Not yet scanned
Last cloaking scan
Capture routing
Local archived 2026-10-16 09:43:10 UTC

Scanner note: alive_content: raw=ok; http=200; via=https_proxy

Live TDS fingerprint check
Seven Keitaro fingerprints and a browser-versus-crawler comparison. A new scan starts only when you press the button.
On demand

No live-check result has been retained.

Timeline & response

1 · outbound report records

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. Threat First Observed 2026-10-16 09:42:10 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as alive pointing to IP 52.37.165.222.
Stored observation history3

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  2. Availability monitor · Recorded state

    Unknown

    probe_inconclusive

  3. Availability monitor · First collection record

    Reachable

Threat Response Pipeline

Discovery
Analysis
Notifications
Monitoring

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

Threat Ingested
peihsi.com detected and queued for full analysis
Oct 16, 2026
URLScan.io Capture
Stored URLScan report with capture artifacts
Oct 16, 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.
OTX Community References
4 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
Oct 16, 2026
Brand Impersonation
Impersonation of Facebook
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
Oct 16, 2026
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results.
Oct 16, 2026
Sent Report Recorded
Stored outgoing record associated with registrar Gransy, s.r.o., 1 abuse contact
abuse@regtons.com
Oct 16, 2026
DestroyList Published
Oct 16, 2026
Monitoring Continues
The domain remains reachable or access-restricted; future checks may update this 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.

Related infrastructure

Shared hosting, registrar records and related domains

Evidence & investigation tools

Original reports, independent checks and evidence links

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20261016-3C109B Recipient: abuse@regtons.com
PDF notice generated Notice text archived (856 chars)
Abuse notice text as sent to the provider
AUP & Terms of Service Violations:
Acceptable Use Policy: Active phishing operations targeting internet users directly violate standard AUP provisions prohibiting fraud and deceptive practices.
Terms of Service: Material breach of service terms regarding malicious use, providing contractual justification for immediate suspension.
Applicable Legal Framework (Unknown):
International Anti-Cybercrime Regulations
Budapest Convention on Cybercrime
Universal Fraud Prevention Laws
Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws.
Investigation Notice: We fully respect your internal investigation processes and discretion. Prompt remediation protects innocent users while mitigating regulatory compliance scrutiny, legal liability, and brand reputation risks associated with ongoing malicious infrastructure.
Deep Analysis

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

Were You Affected by This Site?

5 evidence signal groups linked 1 stored notification records Last known active
If credentials were compromised, report immediately. Do not engage with recovery scammers.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Official reporting routes
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →
Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

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

Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

What information should I collect for my report?

FBI guidelines

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.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including peihsi.com)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
Read the evidence in context

About This Report: peihsi.com

Stored evidence snapshot. Source timestamps appear where available.

Captured title: “PEIHSI 沛曦|Dyson 維修・家電深層清潔|內湖・三重門市”. Apparent target: Facebook.

Stored VirusTotal result for peihsi.com: 92 engines checked. Observed: 2026-10-16 10:13:07 UTC

Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.

Embed this report

A compact widget with a link to the evidence

HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

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