Skip to security report
Recorded security signals
Stored VirusTotal result: 2/92 engines flagged. malicious: 2. suspicious: 0. Analysis time (as stored): 2026-11-02T09:03:52Z. Retrieved (as stored): 2026-11-02T10:49:00Z. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
qr-pedidos.pages.dev favicon

qr-pedidos.pages.dev

In short

The captured page for qr-pedidos.pages.dev shows a Spanish-language interface titled "QR Pedidos" with a settings gear icon. Behind a modal dialog, the main view includes an "Escanear" (Scan) button and a "Detalle" text field prompting the user to write order details. The open "Ajustes" dialog contains an "Enlace de la conexión de Google" field pre-filled with a script.google.com URL, a "Clave de acceso" field, a "Guardar y probar conexión" button, and a collapsed "Más opciones" section.

“QR Pedidos”

Registrar
United StatesCloudflare
Resolved IP
Canada172.66.47.142Cloudflare, Inc. · CDN
First observed
Nov 2, 2026
PhishDestroy assessment High
66/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
VirusTotal detections: 2/92
VirusTotal
engine detections ·
URLScan
engine verdict · score 98
Page captures
open gallery
Nov 2, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded qr-pedidos.pages.dev on 2026-11-02. Stored VirusTotal result: 2/92 engines flagged. malicious: 2. suspicious: 0. Analysis time (as stored): 2026-11-02T09:03:52Z. Retrieved (as stored): 2026-11-02T10:49:00Z. Risk: high (66/100). Registrar: Cloudflare. Status: Last known active. Hosting: Cloudflare, Inc. Do not enter credentials or connect a wallet.

High
Status
Last known active
VirusTotal
2 / 92
Hosting
Canada172.66.47.142Cloudflare, Inc. · CDN
Registrar
United StatesCloudflare
Page captures
4

Capture recorded with this analysis · Cloudflare Radar · 2026-11-02T08:40:04Z
SHA-256: cbbe9ee72fbe1d497fb02cd9aa8f160e6455449518a4f6c10a6faca6ccccaa9b

PhishDestroy analysis, reviewed version

The captured page for qr-pedidos.pages.dev shows a Spanish-language interface titled "QR Pedidos" with a settings gear icon. Behind a modal dialog, the main view includes an "Escanear" (Scan) button and a "Detalle" text field prompting the user to write order details. The open "Ajustes" dialog contains an "Enlace de la conexión de Google" field pre-filled with a script.google.com URL, a "Clave de acceso" field, a "Guardar y probar conexión" button, and a collapsed "Más opciones" section.

The stored VirusTotal domain result reports 2 detections out of 92 engines. SOCRadar reported "phishing"; Gridinsoft reported "phishing".

Source evidenceVirusTotal 2 / 92 8 sources

VirusTotal

2 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
57
Malicious
2
Suspicious
0
Undetected
33

Vendor labels

SOCRadar
phishing
Gridinsoft
phishing

Reputation score

0

Registrar

CloudFlare, Inc.

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    A
    Value
    172.66.47.142
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:310c::ac42:2c72
  • TTL, seconds
    1800
    Type
    SOA
    Responsible mailbox
    dns.cloudflare.com
    Value
    bella.ns.cloudflare.com
  • TTL, seconds
    21600
    Type
    NS
    Value
    bella.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    A
    Value
    172.66.44.114
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:310c::ac42:2f8e
  • TTL, seconds
    21600
    Type
    NS
    Value
    byron.ns.cloudflare.com

DNS records observed

JARM fingerprint

27d40d40d00040d00042d43d00041df04c41293ba84f6efe3a613b22f983e6

Certificate

Subject alternative names
  • *.qr-pedidos.pages.dev
  • qr-pedidos.pages.dev
Issuer
Let's Encrypt / YE1
Serial
6cf98e19e0ac7c30aeb26366662639a97cb
SHA-256
729e236b9b4b93a5df3c0c721572edf5f38fa7381c78f6102197b20aabbdf460
Subject
qr-pedidos.pages.dev
Valid until
Valid from

Registration record

Registrar
CloudFlare, Inc.
Registrar IANA ID
1910
Registrar URL
None
Registered
Updated
Expires
Status
  • clientDeleteProhibited
  • clientTransferProhibited
  • clientUpdateProhibited
  • clientdeleteprohibited
  • clienttransferprohibited
  • clientupdateprohibited
Nameservers
  • adi.ns.cloudflare.com
  • karl.ns.cloudflare.com
DNSSEC
unsigned
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 57,
    "malicious": 2,
    "suspicious": 0,
    "undetected": 33
}
Vendor labels
{
    "SOCRadar": "phishing",
    "Gridinsoft": "phishing"
}
Reputation
0
Registrar
CloudFlare, Inc.
Created
2020-09-02T02:33:29Z
Expires
2026-09-02T02:33:29Z
Updated
2025-03-17T14:56:22Z
First seen
2026-10-17T22:48:31Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "172.66.47.142"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:310c::ac42:2c72"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "bella.ns.cloudflare.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "bella.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.66.44.114"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:310c::ac42:2f8e"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "byron.ns.cloudflare.com"
    }
]
Dns at
2026-11-02T09:09:14Z
Jarm
27d40d40d00040d00042d43d00041df04c41293ba84f6efe3a613b22f983e6
Certificate
{
    "san": [
        "*.qr-pedidos.pages.dev",
        "qr-pedidos.pages.dev"
    ],
    "issuer": "Let's Encrypt / YE1",
    "serial": "6cf98e19e0ac7c30aeb26366662639a97cb",
    "sha256": "729e236b9b4b93a5df3c0c721572edf5f38fa7381c78f6102197b20aabbdf460",
    "subject": "qr-pedidos.pages.dev",
    "valid_to": "2027-01-15T21:46:18Z",
    "valid_from": "2026-10-17T21:46:19Z"
}
Registration record
{
    "registrar": "CloudFlare, Inc.",
    "registrar_iana_id": "1910",
    "registrar_url": "None",
    "created": "2020-09-02T02:33:29Z",
    "updated": "2023-09-04T18:15:07Z",
    "expires": "2026-09-02T02:33:29Z",
    "status": [
        "clientDeleteProhibited",
        "clientTransferProhibited",
        "clientUpdateProhibited",
        "clientdeleteprohibited",
        "clienttransferprohibited",
        "clientupdateprohibited"
    ],
    "nameservers": [
        "adi.ns.cloudflare.com",
        "karl.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}
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
scope
unknown
result_state
observed
numerator
2
denominator
92
malicious
null
suspicious
null
vendors
["Gridinsoft","SOCRadar"]
observed_at
2026-11-02 09:03:52
checked_at
2026-11-02 11:49:01
fetched_at
2026-11-02 10:49:01
time_basis
as stored; legacy timezone not established

URLScan

Malicious · engine verdict · score 98

SHA-256 e1f9e334007306ee2d6cc9074ed286400031ec4164795c782384a9ee24dc9e6d

Open report
URLScanOriginal source recordObserved: 20 fields

Observed: · Retrieved:

Report ID

01a19b64-286e-738a-a193-77a97a9a0f13

Final URL

https://qr-pedidos.pages.dev/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://qr-pedidos.pages.dev/
    From
    http://qr-pedidos.pages.dev/
    Status
    307

IP address

172.66.47.142

Contacted IP addresses

  • 172.66.47.142

Autonomous systems (ASN)

  • 13335

Linked domains

  • docs.google.com

Document hash

e1f9e334007306ee2d6cc9074ed286400031ec4164795c782384a9ee24dc9e6d

Script hashes

  • bc40c8a15196236b2314db0856f72ca0b49980cd5413b8c852a7349f5fee0859
  • c6af74771800246204bff12598b02eb66cedafeb1453f512e99e07f2e85d67cc
  • 6015c89ea17a304204edfada77905c09037a264220bb8c08af725f556ecab7c0

JavaScript globals

  • jsQR

TLS session and certificate

Subject alternative names
  • *.qr-pedidos.pages.dev
  • qr-pedidos.pages.dev
Cipher
AES_128_GCM
Issuer
YE1
Subject
qr-pedidos.pages.dev
Protocol
QUIC
Valid until
Valid from

Domain age, days

15

Registered domain age, days

15

Certificate age, days

15

Certificate validity, days

89

Page requests

6

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
98
Malicious
Yes
Overall verdict
Score
0
Malicious
No

HTTP headers

Server
cloudflare
Content-type
text/html; charset=utf-8
X-content-type-options
nosniff
Referrer-policy
strict-origin-when-cross-origin
Priority
u=0,i
Original source fields · JSON
Uuid
01a19b64-286e-738a-a193-77a97a9a0f13
Final url
https://qr-pedidos.pages.dev/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://qr-pedidos.pages.dev/",
        "from": "http://qr-pedidos.pages.dev/",
        "status": 307
    }
]
Ip
172.66.47.142
Contacted IP addresses
[
    "172.66.47.142"
]
Asns
[
    "13335"
]
Linked domains
[
    "docs.google.com"
]
Document hash
e1f9e334007306ee2d6cc9074ed286400031ec4164795c782384a9ee24dc9e6d
Script hashes
[
    "bc40c8a15196236b2314db0856f72ca0b49980cd5413b8c852a7349f5fee0859",
    "c6af74771800246204bff12598b02eb66cedafeb1453f512e99e07f2e85d67cc",
    "6015c89ea17a304204edfada77905c09037a264220bb8c08af725f556ecab7c0"
]
Globals
[
    "jsQR"
]
Tls
{
    "san": [
        "*.qr-pedidos.pages.dev",
        "qr-pedidos.pages.dev"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE1",
    "subject": "qr-pedidos.pages.dev",
    "protocol": "QUIC",
    "valid_to": "2027-01-15T21:46:18Z",
    "valid_from": "2026-10-17T21:46:19Z"
}
Domain age days
15
Apex age days
15
Tls age days
15
Tls valid days
89
Requests
6
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 98,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=utf-8",
    "x-content-type-options": "nosniff",
    "referrer-policy": "strict-origin-when-cross-origin",
    "priority": "u=0,i"
}
Separate monitor record · date not recorded

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

record_source
domain_monitor.urlscan
uuid
01a19b64-286e-738a-a193-77a97a9a0f13
score
null
malicious
null
result_at
null
enriched_at
2026-11-02T09:10:37Z
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":"2026-11-02 10:10:37"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

no community references

Open report

Cloudflare Radar

provider verdict: clean

Open report
Cloudflare RadarOriginal source recordObserved: 11 fields

Observed: · Retrieved:

Report ID

b6b77741-e0f6-4944-b049-ae49e8644d6f

Final URL

https://qr-pedidos.pages.dev/

HTTP response

200

Navigation history

  • URL
    https://qr-pedidos.pages.dev/
    Status
    200

DOM structure hash

4efe0071ebb4727da29430561fecad26a2335c1a258362f31b0a6d86d7a5369f

Document hash

e1f9e334007306ee2d6cc9074ed286400031ec4164795c782384a9ee24dc9e6d

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    qr-pedidos.pages.dev
    Type
    A
    Value
    172.66.44.114
  • Name
    qr-pedidos.pages.dev
    Type
    A
    Value
    172.66.47.142
  • Name
    qr-pedidos.pages.dev
    Type
    AAAA
    Value
    2606:4700:310c::ac42:2c72
  • Name
    qr-pedidos.pages.dev
    Type
    AAAA
    Value
    2606:4700:310c::ac42:2f8e

DNSSEC valid

No

IP address

127.0.1.37

127.0.1.37 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Registration record

Registrar
CloudFlare, Inc.
Registered
Updated
Expires
Nameservers
  • adi.ns.cloudflare.com
  • karl.ns.cloudflare.com
Original source fields · JSON
Uuid
b6b77741-e0f6-4944-b049-ae49e8644d6f
Final url
https://qr-pedidos.pages.dev/
Status
200
History
[
    {
        "url": "https://qr-pedidos.pages.dev/",
        "status": 200
    }
]
DOM structure hash
4efe0071ebb4727da29430561fecad26a2335c1a258362f31b0a6d86d7a5369f
Document hash
e1f9e334007306ee2d6cc9074ed286400031ec4164795c782384a9ee24dc9e6d
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "qr-pedidos.pages.dev",
        "type": "A",
        "value": "172.66.44.114"
    },
    {
        "name": "qr-pedidos.pages.dev",
        "type": "A",
        "value": "172.66.47.142"
    },
    {
        "name": "qr-pedidos.pages.dev",
        "type": "AAAA",
        "value": "2606:4700:310c::ac42:2c72"
    },
    {
        "name": "qr-pedidos.pages.dev",
        "type": "AAAA",
        "value": "2606:4700:310c::ac42:2f8e"
    }
]
Dnssec valid
false
Ip
127.0.1.37

127.0.1.37 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Registration record
{
    "registrar": "CloudFlare, Inc.",
    "created": "2020-09-02T02:33:29Z",
    "updated": "2026-06-09T12:00:52Z",
    "expires": "2027-09-02T02:33:29Z",
    "nameservers": [
        "adi.ns.cloudflare.com",
        "karl.ns.cloudflare.com"
    ]
}

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

10 / 100 · heuristic score · 1 brand reference · 0 classifications

Open report
Separate monitor score · 10 / 100 · 2026-11-02T10:54:39Z

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

record_source
domain_monitor.dom_analysis
heuristic_score
10
analyzed_at
2026-11-02T10:54:39Z
source_timestamp
2026-11-02 11:54:39
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

ai_title
qr-pedidos.pages.dev: QR Pedidos order scanning and settings page
ai_description
PhishDestroy records qr-pedidos.pages.dev as a Spanish-language QR Pedidos page offering QR scanning, order detail entry, and a Google connection settings dialog.
ai_summary
The captured page for qr-pedidos.pages.dev shows a Spanish-language interface titled "QR Pedidos" with a settings gear icon. Behind a modal dialog, the main view includes an "Escanear" (Scan) button and a "Detalle" text field prompting the user to write order details. The open "Ajustes" dialog contains an "Enlace de la conexión de Google" field pre-filled with a script.google.com URL, a "Clave de acceso" field, a "Guardar y probar conexión" button, and a collapsed "Más opciones" section. The stored VirusTotal domain result reports 2 detections out of 92 engines. SOCRadar reported "phishing"; Gridinsoft reported "phishing".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-11-02 11:50:25
revision
9a6a87ee0a8f8553993d7b705b72ec2450f10e4e8b2ac673cdebebdbe08ed2fa
mode
reviewed
interpretation
Selected public package; text generation time is separate from source observation dates.

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: 22 fields

Mail configuration

SPF lookups
0

CAA records

Domain
qr-pedidos.pages.dev

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Page title and metadata

Page title
QR Pedidos
Theme color
#126b58
Description
Escaneá, escribí el detalle y enviá tu registro.

Trackers

Requests
7

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
2
TLS
28
Waiting
104
Connection
6
Download
0
Response time, ms
140

TLS connection

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

Ports

Open ports
  • 80
  • 443
  • 8080

Carbon estimate

Bytes
3710
CO₂, grams
0.0001
Cleaner than, %
93

DNS servers

Nameservers
  • IP address
    108.162.192.74
    Host
    bella.ns.cloudflare.com
  • IP address
    162.159.44.67
    Host
    byron.ns.cloudflare.com
DNS zone
qr-pedidos.pages.dev

Location

IP address
2606:4700:310c::ac42:2f8e
ASN
13335
Organization
Cloudflare, Inc.
City
Montreal
Country
CA

TLS certificate

Issuer
Let's Encrypt / YE1
Subject
qr-pedidos.pages.dev

DNS records

A
  • 172.66.47.142
  • 172.66.44.114
NS
  • byron.ns.cloudflare.com
  • bella.ns.cloudflare.com
SOA
Primary nameserver
bella.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2419074063
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800
AAAA
  • 2606:4700:310c::ac42:2c72
  • 2606:4700:310c::ac42:2f8e

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
strict-origin-when-cross-origin
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
nosniff
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

Web application firewall

WAF product
Cloudflare
WAF detected
Yes

IP lookup

IP address
2606:4700:310c::ac42:2c72
IP version
6

Redirects

Redirect chain
  • https://qr-pedidos.pages.dev

Page links

External link addresses
  • https://docs.google.com/spreadsheets/d/1-Bs_J5QOeVSNpPzrZxQpm7cYhdEvLFJDkPyqHvaKDGA/edit
External links
1

HTTP headers

Response headers
Server
cloudflare
Content-type
text/html; charset=utf-8
X-content-type-options
nosniff
Referrer-policy
strict-origin-when-cross-origin
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "qr-pedidos.pages.dev"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Page title and metadata
{
    "title": "QR Pedidos",
    "themeColor": "#126b58",
    "description": "Escaneá, escribí el detalle y enviá tu registro."
}
Trackers
{
    "requests": 7
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 2,
        "tls": 28,
        "wait": 104,
        "connect": 6,
        "download": 0
    },
    "response_ms": 140
}
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": [
        80,
        443,
        8080
    ]
}
Carbon
{
    "bytes": 3710,
    "co2_grams": 0.0001,
    "cleaner_than": 93
}
Dns server
{
    "ns": [
        {
            "ip": "108.162.192.74",
            "host": "bella.ns.cloudflare.com"
        },
        {
            "ip": "162.159.44.67",
            "host": "byron.ns.cloudflare.com"
        }
    ],
    "zone": "qr-pedidos.pages.dev"
}
Location
{
    "ip": "2606:4700:310c::ac42:2f8e",
    "asn": "13335",
    "org": "Cloudflare, Inc.",
    "city": "Montreal",
    "country": "CA"
}
Ssl
{
    "issuer": "Let's Encrypt / YE1",
    "subject": "qr-pedidos.pages.dev"
}
DNS records
{
    "A": [
        "172.66.47.142",
        "172.66.44.114"
    ],
    "NS": [
        "byron.ns.cloudflare.com",
        "bella.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"bella.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2419074063, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}",
    "AAAA": [
        "2606:4700:310c::ac42:2c72",
        "2606:4700:310c::ac42:2f8e"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": "strict-origin-when-cross-origin",
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": "nosniff",
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Firewall
{
    "waf": "Cloudflare",
    "has_waf": true
}
Get ip
{
    "ip": "2606:4700:310c::ac42:2c72",
    "family": 6
}
Redirects
{
    "chain": [
        "https://qr-pedidos.pages.dev"
    ]
}
Page links
{
    "external": [
        "https://docs.google.com/spreadsheets/d/1-Bs_J5QOeVSNpPzrZxQpm7cYhdEvLFJDkPyqHvaKDGA/edit"
    ],
    "external_count": 1
}
HTTP headers
{
    "headers": {
        "server": "cloudflare",
        "content-type": "text/html; charset=utf-8",
        "x-content-type-options": "nosniff",
        "referrer-policy": "strict-origin-when-cross-origin"
    }
}

Questions about qr-pedidos.pages.dev

Is qr-pedidos.pages.dev legit?

PhishDestroy rates qr-pedidos.pages.dev as high risk (66/100) from the recorded evidence; it was first recorded on 2026-11-02. Stored VirusTotal result: 2/92 engines flagged. malicious: 2. suspicious: 0. Analysis time (as stored): 2026-11-02T09:03:52Z. Retrieved (as stored): 2026-11-02T10:49:00Z. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is qr-pedidos.pages.dev safe to connect a wallet?

This report does not record which wallet requests qr-pedidos.pages.dev 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.

What should I do if I used qr-pedidos.pages.dev?

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.

Explore

Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Last checked

Stored Capture · 4 captures

All capture links and hashes (4)

Domain details

Domain
IP Context Canada172.66.47.142 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Platform provider Cloudflare US(US)
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedNov 2, 2026
DOM Analysisanalyzed Nov 2, 2026score 10/1001 brand signal
Submitted URLhttp://qr-pedidos.pages.dev/
Favicon Hash
Observed page title
QR Pedidos
Automated brand references
Google
TLS Certificate
Issued by YE1 · stored validity ends in 73 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
Canada172.66.47.142
Network ASN
AS13335
AS name
CLOUDFLARENET - Cloudflare, Inc., US
Organization
Cloudflare, Inc.
Observed location
CanadaMontreal, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • bella.ns.cloudflare.com
  • byron.ns.cloudflare.com

SOA

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

Location describes the IP network.

TLS certificate

Issuer
YE1
Valid from
2026-10-17 21:46:19
Valid until
2027-01-15 21:46:18
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint729e236b9b4b93a5df3c0c721572edf5f38fa7381c78f6102197b20aabbdf460
Certificate names · 2 SANs
  • *.qr-pedidos.pages.dev
  • qr-pedidos.pages.dev

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-02 12:07:48 UTC

The site was serving its pages at the latest check.

Technical details
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-11-02 12:07:48 UTC
RDAP registration
Observed timeline last reachable: 2026-11-02 12:07:48 UTC last content: 2026-11-02 12:07:48 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.
Technologies · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

2 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 2 detections
SOCRadar
Gridinsoft
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of qr-pedidos.pages.dev · checked Nov 2, 2026

100
Good
Performance
FCP
0.8 s
First Contentful Paint
LCP
0.8 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
2.2 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
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.

Captured network requests

Network requests: 6 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-02 08:37 UTC.

Open this scan on URLScan 01a19b64-286e-738a-a193-77a97a9a0f13 ↗

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

    live_content

    content_served

  2. VirusTotal · Detection count

    0→2

    Engines added
    Gridinsoft · SOCRadar
    Engines removed
    None recorded
    Recorded vendor total
    2
  3. Domain monitor · First collection record

    Reachable

All retained availability observations4

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.

  1. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 13:07:48.000000
    Evidence SHA-256
    76e82d963603b042d186c25927993e5121da5e8a253d013e709758b5a279c734
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 13:07:48
    Evidence reason
    alive_content
  2. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 13:07:48.000000
    Evidence SHA-256
    76e82d963603b042d186c25927993e5121da5e8a253d013e709758b5a279c734
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 13:07:48
    Evidence reason
    alive_content
  3. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 09:35:21.000000
    Evidence SHA-256
    81125a3b5984bcfc9435786697cf8c91c8c50f2a678c233985dba3322f4dbc5d
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 09:35:21
    Evidence reason
  4. http_observationunknown
    Observation source
    http_observation
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 09:35:21.000000
    Evidence SHA-256
    81125a3b5984bcfc9435786697cf8c91c8c50f2a678c233985dba3322f4dbc5d
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 09:35:21
    Evidence reason

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. 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: 1 of 1
  • Threat Ingested
    qr-pedidos.pages.dev detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Forensic Evidence Collected · Technical Analysis Recorded · VirusTotal detections +2 Recorded: 7 of 7
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 98
  • Cloudflare Radar Report
    A stored Cloudflare Radar report is available. The report link alone does not mean that the domain was classified as malicious, and it does not prove that every network field was captured.
  • VirusTotal
    Detections recorded on VirusTotal: 2/92
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
  • VirusTotal detections +2
    New detections: +2 (0 → 2): Gridinsoft, SOCRadar
Publication & AvailabilityDestroyList Published · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

3 entries
  1. VirusTotal

    2/92 engine detections

    View source
  2. Added to PhishDestroy

    qr-pedidos.pages.dev

    View source
  3. URLScan

    Page captured

    View source
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.

qr-pedidos.pages.dev

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

3 evidence signal groups linked Last known active
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. Silence is the scammer’s greatest advantage. Break it.
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.

Official reporting routes

More official reporting routes
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.

Report to Your Local Authorities

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

97-country directory

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.

  • 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

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 qr-pedidos.pages.dev)
  • 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.

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.

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/qr-pedidos.pages.dev"
  title="PhishDestroy threat report for qr-pedidos.pages.dev"
  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>