Skip to security report
blogssab.com favicon
Domain security and threat intelligence

blogssab.com

I was scammed — help me write a report
Share / download report
Post on X Send in Telegram Check via API
In short

PhishDestroy first recorded blogssab.com on 2026-11-15. Stored VirusTotal result: 13/92 engines flagged. Malicious: 12. Suspicious: 1. Analysis time (as stored): 2026-11-10 15:08 UTC. Retrieved (as stored): 2026-11-15 15:38 UTC.

Page title: “Blog For New Technology - Blog For New Technology In The World”

More about the sources
Recorded security signals

Stored VirusTotal result: 13/92 engines flagged. Malicious: 12. Suspicious: 1. Analysis time (as stored): 2026-11-10 15:08 UTC. Retrieved (as stored): 2026-11-15 15:38 UTC. Use caution — do not enter credentials or personal information.

VirusTotal detections: 13/92 Last known active
Registrar
United StatesNameCheap
Resolved IP
Canada188.114.96.3CloudFlare, Inc. · CDN
Registered
2023-04-06
First seen by PhishDestroy
2026-11-15
URLQuery
detections
Page captures
open gallery
Domain age
registered 2023-04-06 according to WHOIS
Reports sent
view timeline
2026-11-15 1 Report Sent CDN

Risk score, higher = worse · How this score works

What to do right now

Pick what happened and tick the steps as you go. The ticks are kept only in this browser.

Entered a password0/3
Paid or entered card or bank details0/2
Downloaded a file0/2
Shared a seed phrase or private key0/3
Approved token spending (approve / permit)0/3
Connected a wallet but signed nothing0/2
Sent crypto0/3
Write a police report

Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.

ABUSE NOTICE · 72H+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

The sent-report ledger records the first outgoing report at . The recorded recipient is abuse@namecheap.com. The latest stored availability evidence still shows the domain reachable; 6 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.

Elapsed since first report
6 days
Reports sent
1
Latest case ID
PD-04EDF29B03176585C315
Current status
HTTP 403 at latest stored check

Analysis

Domain summary

PhishDestroy first recorded blogssab.com on 2026-11-15. Stored VirusTotal result: 13/92 engines flagged. Malicious: 12. Suspicious: 1. Analysis time (as stored): 2026-11-10 15:08 UTC. Retrieved (as stored): 2026-11-15 15:38 UTC. Risk: critical (evidence score 98/100). Registrar: NameCheap. Status: Reachable · access restricted. Hosting: Cloudflare, Inc. PhishDestroy sent 1 abuse report. Do not enter credentials or connect a wallet.

Critical
Status
Reachable · access restricted
VirusTotal
13 / 92
Hosting
Canada188.114.96.3CloudFlare, Inc. · CDN
Registrar
United StatesNameCheap
Registered
2023-04-06
Page captures
5

Recorded source summary

PhishDestroy first observed blogssab.com on Nov 15, 2026. The captured page title is “Blog For New Technology - Blog For New Technology In The World”. Current evidence score: 98/100 (critical).

Positive findings are stored from 2 sources: VirusTotal and URLQuery. VirusTotal recorded 13 detections among 92 engines: ESET, VIPRE, G-Data, Lionic, Sophos, Webroot, Fortinet, Gridinsoft, ADMINUSLabs, BitDefender, Chong Lua Dao, alphaMountain.ai, Forcepoint ThreatSeeker on Nov 10, 2026 at 15:08 UTC. URLQuery recorded 2 detections; no observation timestamp was retained.

An access-restricted HTTP 403 response was recorded on Nov 22, 2026 at 11:10 UTC. Latest classified outcome: protected; cause cloudflare challenge; mechanism challenge; observed actor Cloudflare on Nov 22, 2026 at 10:10 UTC. Registration records for the domain list NameCheap, Inc. as the registrar and Apr 6, 2023 as the creation date. At collection time, the hostname resolved to 188.114.96.3 on AS13335 (Cloudflare, Inc.). The IP and ASN identify shared Cloudflare edge infrastructure; the origin server is not established by this address. DOM analysis on Nov 15, 2026 at 19:20 UTC returned 15/100. The evidence archive retains 5 visual captures from PhishDestroy, URLScan, Cloudflare Radar, and URLQuery. TLS metadata lists WE1 as the certificate issuer with validity through Dec 22, 2026.

The content indicators and 2 positive source findings support the current phishing classification.

Source evidenceVirusTotal 13 / 92 7 sources

VirusTotal

13 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 15 fields
Separate collector summary

This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.

Source
VirusTotal
Result state
observed
Numerator
13
Denominator
92
Vendors
ADMINUSLabs, alphaMountain.ai, BitDefender, Chong Lua Dao, ESET, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft, Lionic, Sophos, VIPRE, Webroot
Observed at
2026-11-10 15:08:48
Checked at
2026-11-15 16:38:16
Fetched at
2026-11-15 15:38:17

Gridinsoft

1/100

URLScan

Page capture

SHA-256 33de539b…83c50ce

Open report
URLScanOriginal source recordObserved: 21 fields

PhishDestroy DOM

15 / 100 · heuristic score · 0 brand references · 0 classifications

Content heuristic only; not the final score

Open report

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 17 fields

Mail configuration

MX records
  • _dc-mx.035b3d82a2be.blogssab.com
SPF record
v=spf1 +a +mx +ip4:173.249.52.37 ~all
DKIM
  • default
DKIM key size, bits
2048
SPF lookups
2

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

Last observation
First observation
Recorded changes
44
Archived days
46
Snapshots per day
0.05
Average page size, bytes
18462

TLS connection

ALPN
h2
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1
  • TLSv1.1
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 80
  • 443
  • 8080

DNS servers

Nameservers
  • IP address
    172.64.32.106
    Host
    dawn.ns.cloudflare.com
  • IP address
    108.162.195.238
    Host
    syeef.ns.cloudflare.com
DNS zone
blogssab.com

Page quality

Layout shift (CLS)
0.003
SEO score
40
Speed Index, s
1.59
First Contentful Paint (FCP), s
0.76
Largest Contentful Paint (LCP), s
0.76
Total Blocking Time (TBT), ms
649
Performance score
84
Accessibility score
93
Best practices score
96

Location

IP address
2a06:98c1:3120::3
ASN
13335
Organization
CloudFLARENET-EU
City
London
Country
GB

TLS certificate

Subject alternative names
  • blogssab.com
  • *.blogssab.com
Key size, bits
256
Certificate chain
  • blogssab.com
  • WE1
  • GTS Root R4
Issuer
Google Trust Services / WE1
Serial
93E4B849C367A55F0EC5D579BD91FD57
SHA-256
5d9f45541542ea879a948120d694b3f40239a5fa5321a392bd60a92df5b011e7
Subject
blogssab.com
Valid until
Valid from

DNS records

A
  • 188.114.96.3
  • 188.114.97.3
MX
  • Mail server
    _dc-mx.035b3d82a2be.blogssab.com
    Priority
    0
NS
  • dawn.ns.cloudflare.com
  • syeef.ns.cloudflare.com
SOA
Primary nameserver
dawn.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2415683833
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800
TXT
  • v=spf1 +a +mx +ip4:173.249.52.37 ~all
AAAA
  • 2a06:98c1:3120::3
  • 2a06:98c1:3121::3

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

Web application firewall

WAF product
Cloudflare
WAF detected
Yes

IP lookup

IP address
2a06:98c1:3120::3
IP version
6

TXT records

Records
  • v=spf1 +a +mx +ip4:173.249.52.37 ~all

Technology stack

Technologies
  • AngularJS
  • Cloudflare Turnstile
  • Cloudflare
  • HTTP/3

Registration record

Registrar
NameCheap, Inc.
Registrar IANA ID
1068
Registrar URL
http://www.namecheap.com
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • dawn.ns.cloudflare.com
  • syeef.ns.cloudflare.com
DNSSEC
unsigned

HTTP headers

Response headers
Server
cloudflare
Content-Type
text/html; charset=UTF-8
Content-Security-Policy
default-src 'none'; script-src 'nonce-8e8AL6IYAk7MkXx4xD1KfP' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline'; img-src 'self' https://challenges.cloudflare.com; connect-src 'self' https://challenges.cloudflare.com; frame-src 'self' https://challenge
X-Frame-Options
SAMEORIGIN
X-Content-Type-Options
nosniff
Referrer-Policy
same-origin
Permissions-Policy
accelerometer=(),camera=(),clipboard-read=(),clipboard-write=(),geolocation=(),gyroscope=(),hid=(),magnetometer=(),microphone=(),payment=(),publickey-credentials-get=(),screen-wake-lock=(),serial=(),sync-xhr=(),usb=(),xr-spatial-tracking=*
Cross-Origin-Opener-Policy
same-origin
Cross-Origin-Resource-Policy
same-origin
Cross-Origin-Embedder-Policy
require-corp
Original source fields · JSON
Mail configuration
MX: _dc-mx.035b3d82a2be.blogssab.com; Spf: v=spf1 +a +mx +ip4:173.249.52.37 ~all; Dkim: default; Dkim bits: 2048; Spf lookups: 2
Protective DNS results
Resolvers: 12; Blocked count: 0
Web archive observations
Last: 2026-04-10T05:58:19Z; First: 2023-08-21T06:41:30Z; Changes: 44; Days archived: 46; Scans per day: 0.05; Avg page bytes: 18462
TLS connection
Alpn: h2; Cipher: TLS_AES_256_GCM_SHA384; Protocol: TLSv1.3; Versions: TLSv1, TLSv1.1, TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓
Ports
Open: 80, 443, 8080
DNS server
NS: (IP: 172.64.32.106; Host: dawn.ns.cloudflare.com), (IP: 108.162.195.238; Host: syeef.ns.cloudflare.com); Zone: blogssab.com
Quality
Cls: 0.003; Seo: 40; Si s: 1.59; Fcp s: 0.76; Lcp s: 0.76; Tbt ms: 649; Performance: 84; Accessibility: 93; Best practices: 96
Location
IP: 2a06:98c1:3120::3; ASN: 13335; Org: CloudFLARENET-EU; City: London; Country: GB
SSL
San: blogssab.com, *.blogssab.com; Bits: 256; Chain: blogssab.com, WE1, GTS Root R4; Issuer: Google Trust Services / WE1; Serial: 93E4B849C367A55F0EC5D579BD91FD57; SHA256: 5d9f45541542ea879a948120d694b3f40239a5fa5321a392bd60a92df5b011e7; Subject: blogssab.com; Valid to: 2026-12-22T21:13:04Z; Valid from: 2026-09-23T20:15:22Z
DNS records
A: 188.114.96.3, 188.114.97.3; MX: Exchange: _dc-mx.035b3d82a2be.blogssab.com; Priority: 0; NS: dawn.ns.cloudflare.com, syeef.ns.cloudflare.com; Soa: Nsname: dawn.ns.cloudflare.com; Hostmaster: dns.cloudflare.com; Serial: 2415683833; Refresh: 10000; Retry: 2400; Expire: 604800; Minttl: 1800; Txt: v=spf1 +a +mx +ip4:173.249.52.37 ~all; Aaaa: 2a06:98c1:3120::3, 2a06:98c1:3121::3
Dnssec
Ds: ✗; Rrsig: ✗; Dnskey: ✗
Firewall
Waf: Cloudflare; Has waf: ✓
Get IP
IP: 2a06:98c1:3120::3; Family: 6
Txt records
Records: v=spf1 +a +mx +ip4:173.249.52.37 ~all
Tech stack
Technologies: AngularJS, Cloudflare Turnstile, Cloudflare, HTTP/3
Registration record
Registrar: NameCheap, Inc.; Registrar iana ID: 1068; Registrar URL: http://www.namecheap.com; Created: 2023-04-06T19:22:08Z; Updated: 2026-04-12T09:32:00Z; Expires: 2027-04-06T19:22:08Z; Status: clientTransferProhibited https://icann.org/epp; Nameservers: dawn.ns.cloudflare.com, syeef.ns.cloudflare.com; Dnssec: unsigned
HTTP headers
Headers: Server: cloudflare; Content type: text/html; charset=UTF-8; Content security policy: default-src 'none'; script-src 'nonce-8e8AL6IYAk7MkXx4xD1KfP' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline'; img-src 'self' https://challenges.cloudflare.com; connect-src 'self' https://challenges.cloudflare.com; frame-src 'self' https://challenge; X frame options: SAMEORIGIN; X content type options: nosniff; Referrer policy: same-origin; Permissions policy: accelerometer=(),camera=(),clipboard-read=(),clipboard-write=(),geolocation=(),gyroscope=(),hid=(),magnetometer=(),microphone=(),payment=(),publickey-credentials-get=(),screen-wake-lock=(),serial=(),sync-xhr=(),usb=(),xr-spatial-tracking=*; Cross origin opener policy: same-origin; Cross origin resource policy: same-origin; Cross origin embedder policy: require-corp
Security Signals
SA Scamadviser Warnings 21/100
The website's owner is hiding his identity on WHOIS using a paid service This website does not have many visitors Several spammers and scammers use the same registrar No reviews were found on commonly used review sites Malware has been detected on this site by iQ Abuse Scan
This site seems to sell products online (how to check if it is a shop scam) According to the SSL check the certificate is valid This website has existed for quite some years DNSFilter considers this website safe

Questions about blogssab.com

Is blogssab.com legit?

PhishDestroy rates blogssab.com as critical risk (evidence score 98/100) from the recorded evidence; it was first recorded on 2026-11-15. Stored VirusTotal result: 13/92 engines flagged. Malicious: 12. Suspicious: 1. Analysis time (as stored): 2026-11-10 15:08 UTC. Retrieved (as stored): 2026-11-15 15:38 UTC. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is blogssab.com safe to connect a wallet?

Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on blogssab.com. A confirmed blockchain transaction cannot be reversed.

What should I do if I used blogssab.com?

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
  • Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
  • Approved token spending (approve / permit) — revoke that approval with a token-approval checker
  • Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
  • 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.

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Page captures (5)

All capture links and hashes (5)

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 72 report ↗
IP Context Canada188.114.96.3 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar NameCheap US(US)
RegistrationCreated 2023-04-06 — Expires 2027-04-06
Registrant countryUnited States VirusTotal WHOIS
Registrant3b5f76ecd769308fd9c4dfbbcdb34678s@withheldforprivacy.com VirusTotal WHOIS
HTTP Status403 Forbidden
Technical detailsProvenance & timestamps
First Detected2026-11-15
DOM Analysisanalyzed 2026-11-15score 15/100
Submitted URLhttp://blogssab.com/
Favicon Hash
Case ID
Observed page title
Blog For New Technology - Blog For New Technology In The World
TLS Certificate
Issued by WE1 · stored validity ends in 30 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
Canada188.114.96.3
Network ASN
AS13335
Organization
CloudFlare, Inc.
Observed location
CanadaToronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • dawn.ns.cloudflare.com
  • syeef.ns.cloudflare.com

SOA

  • nsname: dawn.ns.cloudflare.com
  • hostmaster: dns.cloudflare.com
  • serial: 2415683833
  • refresh: 10000
  • retry: 2400
  • expire: 604800
  • minttl: 1800

Registrar abuse contact VirusTotal WHOIS

Mail routing 1 MX record

  • _dc-mx.035b3d82a2be.blogssab.compriority 0

Location describes the IP network.

TLS certificate

Issuer
WE1
Valid from
2026-09-23 20:15:22
Valid until
2026-12-22 21:13:04
Hostname match
Yes
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint5d9f45541542ea879a948120d694b3f40239a5fa5321a392bd60a92df5b011e7
Certificate names · 2 SANs
  • blogssab.com
  • *.blogssab.com

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-11-22 11:10 UTC

The site was reachable but behind an access challenge at the latest check.

Technical details
Primary outcome Reachable but protected reason: Cloudflare Challenge 85% confidence
Attribution Cloudflare mechanism: Challenge source: Current Http Probe
Evidence layers Availability: Reachable but protected DNS: Resolved
Latest HTTP observation Reachable but protected Cloudflare Challenge Cloudflare Challenge 85% 2026-11-22 11:10 UTC
RDAP registration
Observed timeline last reachable: 2026-11-22 11:10 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 subdomains8

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

  • cpanel.blogssab.comDomain record
  • cpcalendars.blogssab.comDomain record
  • cpcontacts.blogssab.comDomain record
  • mail.blogssab.comDomain record
  • webdisk.blogssab.comDomain record
  • webmail.blogssab.comDomain record
  • www.blogssab.comDomain record
  • www.cpcontacts.blogssab.comDomain record
Technologies · 2 identified
Open complete records

VirusTotal Analysis

13 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive result retrieved by PhishDestroy
ESET
VIPRE
G-Data
Lionic
Sophos
Webroot
Fortinet
Gridinsoft
ADMINUSLabs
BitDefender
Chong Lua Dao
alphaMountain.ai
Forcepoint ThreatSeeker
PageSpeed (mobile): 95

Google PageSpeed Insights — mobile performance audit of blogssab.com ·

95
Good
Performance
FCP
0.76 s
First Contentful Paint
LCP
0.76 s
Largest Contentful Paint
CLS
0.003
Cumulative Layout Shift
TBT
265 ms
Total Blocking Time
SI
1.22 s
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 403
Requested URL: http://blogssab.com/
Final URL: https://blogssab.com/
Just a moment...
Response
HTTP 403
HTML body
5.4 KB
Compressed
3.2 KB
Links
0 internal · 0 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html; charset=UTF-8
CF-Mitigated: challenge
Server: cloudflare
Content-Encoding: gzip
Security headers present
Content-Security-PolicyX-Frame-OptionsX-Content-Type-OptionsReferrer-PolicyPermissions-PolicyCross-Origin-Opener-PolicyCross-Origin-Resource-Policy
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 23
Accept-CH
Sec-CH-UA-Bitness, Sec-CH-UA-Arch, Sec-CH-UA-Full-Version, Sec-CH-UA-Mobile, Sec-CH-UA-Model, Sec-CH-UA-Platform-Version, Sec-CH-UA-Full-Version-List, Sec-CH-UA-Platform, Sec-CH-UA, UA-Bitness, UA-Arch, UA-Full-Version, UA-Mobile, UA-Model,
Alt-Svc
h3=":443"; ma=86400
Cf-Mitigated
challenge
CF-RAY
a5af57514e04b918-AMS
Connection
close
Content-Encoding
gzip
Content-Security-Policy
default-src 'none'; script-src 'nonce-gFj2xy0ZosOMCV3DWChRnL' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline'; img-src 'self' https://challenges.cloudflare.com; connect-src 'self' https://challenges.cloudflare.com; frame-src 'self' https://challenges.cloudflare.com blo
Content-Type
text/html; charset=UTF-8
Critical-Ch
Sec-CH-UA-Bitness, Sec-CH-UA-Arch, Sec-CH-UA-Full-Version, Sec-CH-UA-Mobile, Sec-CH-UA-Model, Sec-CH-UA-Platform-Version, Sec-CH-UA-Full-Version-List, Sec-CH-UA-Platform, Sec-CH-UA, UA-Bitness, UA-Arch, UA-Full-Version, UA-Mobile, UA-Model,
Cross-Origin-Embedder-Policy
require-corp
Cross-Origin-Opener-Policy
same-origin
Cross-Origin-Resource-Policy
same-origin
Date
Sun, 15 Nov 2026 15:38:06 GMT
NEL
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Origin-Agent-Cluster
?1
Permissions-Policy
accelerometer=(),camera=(),clipboard-read=(),clipboard-write=(),geolocation=(),gyroscope=(),hid=(),magnetometer=(),microphone=(),payment=(),publickey-credentials-get=(),screen-wake-lock=(),serial=(),sync-xhr=(),usb=(),xr-spatial-tracking=*
Referrer-Policy
same-origin
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=mnu39NiwCFhwnfekc39d9B1q8IuA%2FoU1yN2zQgxY1K3RlyfJdYUfxZbqq8a0U0%2FUX%2FqrpVIUg%2BXkIoprYtf24QtfzJobsDHZ0qLdRy7nB%2FDfIozqY3neDN%2FtDjGphd4%3D"
Server
cloudflare
Server-Timing
chlray;desc="a5af57514e04b918"
Transfer-Encoding
chunked
X-Content-Type-Options
nosniff
X-Frame-Options
SAMEORIGIN

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

Registration & observation details2

Availability observations

Last reachable 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.

All stored data118
Open complete records

Captured network requests

Network requests: 9 SHA-256 hashes: 6 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-15 15:37 UTC.

Open this scan on URLScan 01a1dfd9-7a37-753d-93d0-9719b1d4ad7a ↗

Stored observation history8

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

    Behind a check page or access restriction

    Cloudflare check page · Cloudflare · check page

  2. Availability monitor · Recorded state

    Behind a check page or access restriction

    Cloudflare check page · Cloudflare · check page

  3. Availability monitor · Recorded state

    Behind a check page or access restriction

    Cloudflare check page · Cloudflare · check page

  4. Availability monitor · Recorded state

    Behind a check page or access restriction

    Cloudflare check page · Cloudflare · check page

  5. Availability monitor · Recorded state

    Behind a check page or access restriction

    Cloudflare check page · Cloudflare · check page

Earlier observations 3
  1. Availability monitor · Recorded state

    Behind a check page or access restriction

    Cloudflare check page · Cloudflare · check page

  2. Availability monitor · Recorded state

    Behind a check page or access restriction

    Cloudflare check page · Cloudflare · check page

  3. Domain monitor · First collection record

    Reachable

Separate monitor HTTP observation

Source: domain_monitor. This stored snapshot does not establish current availability.

Observed · UTC
Recorded HTTP status
403
Probe value as recorded
403
Original source timestamp
2026-11-15 16:28:15
All retained availability observations23
Open complete records

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Notifications · recorded
  4. Monitoring · in progress

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

Pre-emptive Discovery & IngestionThreat Ingested recorded
  • Threat Ingested
    blogssab.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Forensic Evidence Collected · Technical Analysis Recorded recorded
Notification RecordsSent Report Recorded recorded
  • Sent Report Recorded
    Stored record of an abuse report about this domain; registrar at the time: NAMECHEAP INC. Abuse contacts: 1.
    • abuse@namecheap.com
Publication & AvailabilityDestroyList Published · Monitoring Continues ongoing
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.
    ongoing

Recorded activity

5 entries

Lifecycle

  1. Domain registered
  2. VirusTotal analysis with detections+1313 d 19 h
  3. Added to PhishDestroy+5 d 0 h
  4. First abuse report sent+2 min

Reported 1318 d 20 h after registration

  1. Namecheap

    Acknowledged the report

    same minute
  2. Abuse report sent

    PD-04EDF29B03176585C315 · Receipt 84953

    abuse@namecheap.com
    +2 min
  3. Added to PhishDestroy

    blogssab.com

    same minute
  4. URLScan

    Page captured

    +5 d 0 h
  5. VirusTotal

    13/92 engine detections

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.

All stored records by source

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

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

blogssab.com

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-04EDF29B03176585C315 Recipient: abuse@namecheap.com
Page title stored with report: Just a moment...
PDF notice generated
Deep Analysis

Were You Affected by This Site?

You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Secure your accounts and funds first, then report. If credentials were compromised, report immediately. Do not engage with recovery scammers.

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.

Where to report

The draft stays only with you.

First secure your money: call your bank or revoke wallet approvals. Immediate steps →

More: international and crypto channels

Official reporting routes

More official reporting routes
SEAL 911 Worldwide

Emergency help from security researchers when a crypto wallet is being drained right now.

FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

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.

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
  • Downloaded a file — do not open it and scan the device with security software
  • Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
  • Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
  • Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
  • Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed

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 blogssab.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

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 →
About this reportSources, observation dates and corrections

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.

Embed this reportA 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/blogssab.com"
  title="PhishDestroy threat report for blogssab.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>