Cloudflare Radar
Suspicious
Open reportguclusirin.com: VirusTotal 0/92 detections. First recorded 2026-10-28. Registrar: Realtime Register B.V.
Page title: “Şirin Baba Panel”
Use caution — do not enter credentials or personal information.
Risk score, higher = worse · How this score works
Pick what happened and tick the steps as you go. The ticks are kept only in this browser.
Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.
PhishDestroy analysis, earlier unreviewed version
PhishDestroy’s automated intake on 2026-10-28 added guclusirin.com to its internal blocklist because the domain was brand‑new and an AI model assigned a 90 % confidence that the page is a phishing site. The page that was fetched returned HTTP 200 and displayed a Turkish‑language login portal titled “Şirin Baba Panel” with fields for username and password, which the prior assessment flagged as a generic credential‑theft interface. The domain was first seen by PhishDestroy on the same day it was registered, 2026-10-28.
Credential‑phishing sites typically present a convincing login form that mimics a legitimate service, capture entered usernames and passwords, and then reuse those credentials to gain unauthorized access to victim accounts. They often use generic branding to avoid drawing attention to a specific target, and the collected credentials can be sold or used in automated account‑takeover attacks. No evidence on this page shows additional malicious behavior beyond the credential‑capture form.
VirusTotal scanned the domain on 2026-10-28 with 92 engines and reported zero malicious or suspicious detections. Google Safe Browsing checked the same day and did not flag the URL. OTX listed no pulses for the domain as of 2026-10-28, and URLScan captured the site on that date, where its machine‑learning engine labeled it malicious with a score of 56 while the overall verdict was non‑malicious. PhishDestroy’s internal blocklist marks the domain as malicious and Cloudflare Radar flagged it as a newly seen domain with security risks.
The domain was registered on 2026-10-28 through Realtime Register B.V., using the nameservers a2.share-dns.com and b2.share-dns.net. The recorded IP was 31.56.209.110, associated with Swissnet LLC in the Netherlands. The site presented a Let’s Encrypt TLS certificate issued on the registration day, valid until 2027-01-26, and the server identified itself as nginx/1.20.1 with ports 22, 80, 443 and 8080 open.
Users should not submit any credentials on guclusirin.com and should change passwords on any service where the same credentials may have been used. Organizations should block the domain at DNS or web‑proxy level, monitor for login attempts using harvested credentials, and review logs for connections to the recorded IP address. PhishDestroy’s blocklist entry can be used to automate denial of future traffic to this exact host.
Suspicious
Open reportPage capture
SHA-256 e5f9a914…bb8790c
Separate stored monitor snapshot; does not replace the primary report record or establish current availability.
Narrative generation metadata
Open reportThe narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.
Results 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 | Spf lookups: 0 |
|---|---|
| Caa records | Domain: guclusirin.com |
| Protective DNS results | Resolvers: 12; Blocked count: 0 |
| Web archive observations | Last: 2026-10-28T14:21:11Z; First: 2019-03-15T01:17:52Z; Changes: 2; Days archived: 9; Scans per day: 0; Avg page bytes: 395 |
| Trackers | Requests: 16 |
| Forms and mixed content | Third party scripts: 0 |
| Status | Up: ✓; Code: 200; Timings: DNS: 40; TLS: 22; Wait: 123; Connect: 30; Download: 0; Response ms: 215 |
| TLS connection | Alpn: h2; Cipher: TLS_AES_256_GCM_SHA384; Protocol: TLSv1.3; Versions: TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓ |
| Ports | Open: 22, 80, 443, 8080 |
| Carbon | Bytes: 172; Co2 grams: 0; Cleaner than: 95 |
| DNS server | NS: (IP: 162.159.27.88; Host: b.share-dns.net), (IP: 172.64.53.25; Host: a.share-dns.com); Zone: guclusirin.com |
| Cookies | Cookies: (Name: Tb ok; Same site: Lax), (Name: sl-session; HTTP only: ✓) |
| Location | IP: 31.56.209.110; ASN: 209373; Org: Swissnet LLC; City: Eygelshoven; Country: NL |
| SSL | Issuer: Let's Encrypt / YE1; Subject: guclusirin.com |
| DNS records | A: 31.56.209.110; NS: a.share-dns.com, b.share-dns.net; Soa: Nsname: a.share-dns.com; Hostmaster: master.share-dns.com; Serial: 1793190089; Refresh: 3600; Retry: 1200; Expire: 86400; Minttl: 600 |
| Dnssec | Ds: ✗; Rrsig: ✗; Dnskey: ✗ |
| Hsts | Message: Site does not serve any HSTS headers. |
| HTTP security policies | Xframeoptions: ✗; Referrerpolicy: ✗; Xxssprotection: ✗; Permissionspolicy: ✗; Xcontenttypeoptions: ✗; Contentsecuritypolicy: ✗; Stricttransportpolicy: ✗; Crossoriginopenerpolicy: ✗; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗ |
| Get IP | IP: 31.56.209.110; Family: 4 |
| Redirects | Chain: https://guclusirin.com |
| Subdomains | Count: 1; Subdomains: www.guclusirin.com |
| Registration record | Registrar: Realtime Register B.V.; Created: 2026-10-28T12:08:09Z; Updated: 2026-10-28T12:16:17Z; Expires: 2027-10-28T12:08:09Z; Status: clientTransferProhibited https://icann.org/epp; Nameservers: a2.share-dns.com, b2.share-dns.net |
| HTTP headers | Headers: Server: nginx/1.20.1; Content type: text/html |
a.share-dns.coma2.share-dns.comb.share-dns.netb2.share-dns.netnsname: a.share-dns.comhostmaster: master.share-dns.comserial: 1793190089refresh: 3600retry: 1200expire: 86400minttl: 600Location describes the IP network.
0f930793bbe222b174e952da1d887a01f685c84146c1f1dcd44b8baf530a48aeguclusirin.comwww.guclusirin.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.
www.guclusirin.comDomain recordGoogle PageSpeed Insights — mobile performance audit of guclusirin.com ·
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Network requests: 22 SHA-256 hashes: 17 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-10-29 01:53 UTC.
Open this scan on URLScan 01a182e1-9e06-73ef-a1a5-6594496f7f20 ↗
Loads saved data; the suspicious site is not opened.
| # | 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.
Redirecting elsewhere
HTTP redirect
Unavailable→Reachable
Reachable→Unavailable
Redirecting elsewhere
HTTP redirect
Redirecting elsewhere
HTTP redirect
Redirecting elsewhere
HTTP redirect
Unavailable→Reachable
Reachable→Unavailable
Redirecting elsewhere
HTTP redirect
Redirecting elsewhere
HTTP redirect
Serving page content→Redirecting elsewhere
HTTP redirect
Serving page content
page content returned
Reachable
Recorded events: 13. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Lifecycle
Reported 2 h 20 min after registration
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.
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.
guclusirin.com PD-20261028-AC84C7 Recipient: abuse@swissnetwork.co 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.
The draft stays only with you.
First secure your money: call your bank or revoke wallet approvals. Immediate steps →
Emergency help from security researchers when a crypto wallet is being drained right now.
Report 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.
Helpline1930Choose 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 ↗
guclusirin.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.