Skip to security report
This domain has been flagged as malicious
Security engines reporting a detection: 14. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
server-security-page--suebru300.replit.app favicon

server-security-page--suebru300.replit.app

In short

PhishDestroy records the captured sign-in page at server-security-page--suebru300.replit.app, whose HTML title reads "Sign in to your account".

“Sign in to your account”

Registrar
Replit
Resolved IP
United States34.117.33.233Google LLC
Registered
Apr 16, 2021
First observed
Oct 31, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
VirusTotal detections: 14/92
VirusTotal
engine detections ·
URLScan
Cloudflare Radar
Page captures
open gallery
Domain age
registered 2021-04-16 according to RDAP · source data differ
Oct 31, 2026
X Telegram API

Analysis

Domain summary

PhishDestroy records the captured sign-in page at server-security-page--suebru300.replit.app, whose HTML title reads "Sign in to your account".

Critical
Status
Last known active
VirusTotal
14 / 92
Hosting
United States34.117.33.233Google LLC
Registrar
Replit
Registered
Apr 16, 2021
Page captures
4

PhishDestroy analysis, reviewed version

The captured page for server-security-page--suebru300.replit.app shows a soft pastel gradient background with no visible sign-in form, heading, or logo, even though the HTML title reads "Sign in to your account". The only visible elements are a small "Made with Replit" badge and links for terms of use and privacy and cookies in the lower-right corner, so the main interaction could not be observed in this capture.

The stored VirusTotal domain result reports 14 detections out of 92 engines. DNS8 reported "phishing"; ESET reported "phishing".

Source evidenceVirusTotal 14 / 92 8 sources

VirusTotal

14 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 12 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
47
Malicious
14
Suspicious
0
Undetected
31

Vendor labels

DNS8
phishing
ESET
phishing
VIPRE
phishing
G-Data
phishing
Emsisoft
phishing
Fortinet
phishing
Netcraft
malicious
SOCRadar
phishing
URLQuery
malicious
Kaspersky
phishing
LevelBlue
phishing
Gridinsoft
phishing
BitDefender
phishing
alphaMountain.ai
phishing

Reputation score

0

Tags

  • dga

Categories

alphaMountain.ai
Information Technology, Phishing (alphaMountain.ai)

Created

Updated

First seen

DNS records

  • TTL, seconds
    3600
    Type
    A
    Value
    34.117.33.233

DNS records observed

JARM fingerprint

29d3fd00029d29d00042d43d00041d6f940079659edb62e1c38c38bd26ee84

Certificate

Subject alternative names
  • replit.app
  • *.replit.app
Issuer
Google Trust Services / WR3
Serial
ec3ae2dfc6c55a2e109aff41a0e4b4c3
SHA-256
9d66dbe59ada0a41e27e591854785cf65280827d651cc4eab47765cf85053250
Subject
replit.app
Valid until
Valid from
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 47,
    "malicious": 14,
    "suspicious": 0,
    "undetected": 31
}
Vendor labels
{
    "DNS8": "phishing",
    "ESET": "phishing",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Emsisoft": "phishing",
    "Fortinet": "phishing",
    "Netcraft": "malicious",
    "SOCRadar": "phishing",
    "URLQuery": "malicious",
    "Kaspersky": "phishing",
    "LevelBlue": "phishing",
    "Gridinsoft": "phishing",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing"
}
Reputation
0
Tags
[
    "dga"
]
Categories
{
    "alphaMountain.ai": "Information Technology, Phishing (alphaMountain.ai)"
}
Created
2021-04-16T00:00:00Z
Updated
2025-12-04T00:00:00Z
First seen
2026-10-30T01:08:24Z
DNS records
[
    {
        "ttl": 3600,
        "type": "A",
        "value": "34.117.33.233"
    }
]
Dns at
2026-10-30T12:50:15Z
Jarm
29d3fd00029d29d00042d43d00041d6f940079659edb62e1c38c38bd26ee84
Certificate
{
    "san": [
        "replit.app",
        "*.replit.app"
    ],
    "issuer": "Google Trust Services / WR3",
    "serial": "ec3ae2dfc6c55a2e109aff41a0e4b4c3",
    "sha256": "9d66dbe59ada0a41e27e591854785cf65280827d651cc4eab47765cf85053250",
    "subject": "replit.app",
    "valid_to": "2027-01-26T05:47:40Z",
    "valid_from": "2026-10-28T04:51:45Z"
}
Separate source record · 14 malicious + 0 suspicious / 92 · 2026-10-30 12:45:00 UTC

The summary above and this provider record were collected at different times. Both remain available; malicious and suspicious classifications are shown separately.

record_source
collected_observations.vt
analysis_at
2026-10-30T12:45:00Z
fetched_at
2026-10-31T22:55:51Z
stats
{"timeout":0,"harmless":47,"malicious":14,"suspicious":0,"undetected":31}

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 15 fields

Observed: · Retrieved:

Report ID

9bb8c566-c0e1-4e1f-843f-7ebb4ab9cce7

Final URL

https://server-security-page--suebru300.replit.app/

HTTP response

200

Navigation history

  • URL
    https://server-security-page--suebru300.replit.app/
    Status
    200

DOM structure hash

184f82ea2d97d6c1f2bb7b165fa6db530f982b752a8e0cc07cdd7af30f5ad3b1

Document hash

f9baed07c86fe634be5334c0d4251cc68f675064c4a00a69bd50ded2554efd7e

Phishing flags

  • Credential Harvester

Phishing classifier result

  • phishing

URL risk categories

  • Phishing

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    server-security-page--suebru300.replit.app
    Type
    A
    Value
    34.117.33.233

DNSSEC valid

No

IP address

127.0.1.1

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

Verdict

Tags
  • phishing
  • Credential Harvester
Malicious
Yes
Categories
  • phishing

Registration record

Registrar
Nom-IQ Limited dba Com Laude
Registered
Updated
Expires
Nameservers
  • ns-cloud-b1.googledomains.com
  • ns-cloud-b2.googledomains.com
  • ns-cloud-b3.googledomains.com
  • ns-cloud-b4.googledomains.com
Original source fields · JSON
Uuid
9bb8c566-c0e1-4e1f-843f-7ebb4ab9cce7
Final url
https://server-security-page--suebru300.replit.app/
Status
200
History
[
    {
        "url": "https://server-security-page--suebru300.replit.app/",
        "status": 200
    }
]
DOM structure hash
184f82ea2d97d6c1f2bb7b165fa6db530f982b752a8e0cc07cdd7af30f5ad3b1
Document hash
f9baed07c86fe634be5334c0d4251cc68f675064c4a00a69bd50ded2554efd7e
Phishing
[
    "Credential Harvester"
]
Phishing v2
[
    "phishing"
]
Url risks
[
    "Phishing"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "server-security-page--suebru300.replit.app",
        "type": "A",
        "value": "34.117.33.233"
    }
]
Dnssec valid
false
Ip
127.0.1.1

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

Verdict
{
    "tags": [
        "phishing",
        "Credential Harvester"
    ],
    "malicious": true,
    "categories": [
        "phishing"
    ]
}
Registration record
{
    "registrar": "Nom-IQ Limited dba Com Laude",
    "created": "2021-04-16T20:44:58Z",
    "updated": "2025-10-10T03:54:10Z",
    "expires": "2034-04-16T20:44:58Z",
    "nameservers": [
        "ns-cloud-b1.googledomains.com",
        "ns-cloud-b2.googledomains.com",
        "ns-cloud-b3.googledomains.com",
        "ns-cloud-b4.googledomains.com"
    ]
}

URLScan

Malicious

SHA-256 f9baed07c86fe634be5334c0d4251cc68f675064c4a00a69bd50ded2554efd7e

Open report
URLScanOriginal source recordObserved: 23 fields

Observed: · Retrieved:

Report ID

01a19425-af07-7087-b761-a1809f4abfe6

Final URL

https://server-security-page--suebru300.replit.app/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://server-security-page--suebru300.replit.app/
    From
    http://server-security-page--suebru300.replit.app/
    Status
    307

IP address

34.117.33.233

Reverse DNS (PTR)

233.33.117.34.bc.googleusercontent.com

Contacted domains

  • aadcdn.msauth.net
  • aadcdn.msftauth.net
  • lomiva.vu
  • replit-cdn.com
  • code.jquery.com

Contacted IP addresses

  • 185.221.216.117
  • 35.190.3.23
  • 2620:1ec:bdf::44
  • 2a02:26f0:3500:c::5c7b:682c
  • 2a04:4e42:200::411
  • 34.117.33.233

Autonomous systems (ASN)

  • 393960
  • 396982
  • 8075
  • 20940
  • 54113

Server countries

  • GB
  • US
  • DE

Linked domains

  • passwordreset.microsoftonline.com
  • www.microsoft.com
  • privacy.microsoft.com

Document hash

f9baed07c86fe634be5334c0d4251cc68f675064c4a00a69bd50ded2554efd7e

JavaScript globals

  • $
  • jQuery
  • inputpw

Cookies

  • GAESA

TLS session and certificate

Subject alternative names
  • replit.app
  • *.replit.app
Cipher
AES_128_GCM
Issuer
WR3
Subject
replit.app
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

1

Differs from the registration date in RDAP (2021-04-16), which gives 2024 days on the scan date 2026-10-31. The two sources disagree; both values are kept as recorded.

Registered domain age, days

1

Differs from the registration date in RDAP (2021-04-16), which gives 2024 days on the scan date 2026-10-31. The two sources disagree; both values are kept as recorded.

Certificate age, days

3

Certificate validity, days

90

Page requests

9

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
100
Malicious
Yes
Overall verdict
Tags
  • phishing
Score
100
Brands
  • microsoft
Malicious
Yes
Categories
  • phishing
URLScan verdict
Tags
  • phishing
Score
100
Brands
  • Microsoft
Malicious
Yes
Categories
  • phishing

HTTP headers

Server
Google Frontend
Content-type
text/html; charset=utf-8
Strict-transport-security
max-age=63072000; includeSubDomains
Original source fields · JSON
Uuid
01a19425-af07-7087-b761-a1809f4abfe6
Final url
https://server-security-page--suebru300.replit.app/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://server-security-page--suebru300.replit.app/",
        "from": "http://server-security-page--suebru300.replit.app/",
        "status": 307
    }
]
Ip
34.117.33.233
Ptr
233.33.117.34.bc.googleusercontent.com
Contacted domains
[
    "aadcdn.msauth.net",
    "aadcdn.msftauth.net",
    "lomiva.vu",
    "replit-cdn.com",
    "code.jquery.com"
]
Contacted IP addresses
[
    "185.221.216.117",
    "35.190.3.23",
    "2620:1ec:bdf::44",
    "2a02:26f0:3500:c::5c7b:682c",
    "2a04:4e42:200::411",
    "34.117.33.233"
]
Asns
[
    "393960",
    "396982",
    "8075",
    "20940",
    "54113"
]
Countries
[
    "GB",
    "US",
    "DE"
]
Linked domains
[
    "passwordreset.microsoftonline.com",
    "www.microsoft.com",
    "privacy.microsoft.com"
]
Document hash
f9baed07c86fe634be5334c0d4251cc68f675064c4a00a69bd50ded2554efd7e
Globals
[
    "$",
    "jQuery",
    "inputpw"
]
Cookies
[
    "GAESA"
]
Tls
{
    "san": [
        "replit.app",
        "*.replit.app"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WR3",
    "subject": "replit.app",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-26T05:47:40Z",
    "valid_from": "2026-10-28T04:51:45Z"
}
Domain age days
1

Differs from the registration date in RDAP (2021-04-16), which gives 2024 days on the scan date 2026-10-31. The two sources disagree; both values are kept as recorded.

Apex age days
1

Differs from the registration date in RDAP (2021-04-16), which gives 2024 days on the scan date 2026-10-31. The two sources disagree; both values are kept as recorded.

Tls age days
3
Tls valid days
90
Requests
9
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 100,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "microsoft"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "Microsoft"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    }
}
HTTP headers
{
    "server": "Google Frontend",
    "content-type": "text/html; charset=utf-8",
    "strict-transport-security": "max-age=63072000; includeSubDomains"
}
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
01a19425-af07-7087-b761-a1809f4abfe6
score
null
malicious
null
result_at
null
enriched_at
null
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":null}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

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

Open report
Separate monitor score · 0 / 100 · 2026-10-31T23:07:52Z

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
0
analyzed_at
2026-10-31T23:07:52Z
source_timestamp
2026-11-01 00:07:52
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
server-security-page--suebru300.replit.app sign-in page capture
ai_description
PhishDestroy records the captured sign-in page at server-security-page--suebru300.replit.app, whose HTML title reads "Sign in to your account".
ai_summary
The captured page for server-security-page--suebru300.replit.app shows a soft pastel gradient background with no visible sign-in form, heading, or logo, even though the HTML title reads "Sign in to your account". The only visible elements are a small "Made with Replit" badge and links for terms of use and privacy and cookies in the lower-right corner, so the main interaction could not be observed in this capture. The stored VirusTotal domain result reports 14 detections out of 92 engines. DNS8 reported "phishing"; ESET reported "phishing".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-10-31 23:57:19
revision
a018de49118b73945a0f0dee61d69644682da95986bf0cc57dbde40cb7bdd73b
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: 23 fields

Mail configuration

SPF lookups
0

CAA records

Domain
server-security-page--suebru300.replit.app

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Crawler rules

User agents
  • *
Present
Yes

Page title and metadata

Page title
Sign in to your account
Indexing directives
none

Trackers

Requests
8
Observed services
  • Name
    jQuery
    Company
    JS Foundation
    Country
    US
    Category
    Hosting
    Requests
    1

Forms and mixed content

Scripts without SRI
  • https://replit-cdn.com/replit-pill/replit-pill.global.js
  • https://code.jquery.com/jquery-3.1.1.min.js
Third-party scripts
2

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
133
TLS
20
Waiting
60
Connection
100
Download
17
Response time, ms
330

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

Carbon estimate

Bytes
114160
CO₂, grams
0.0042
Cleaner than, %
19

DNS servers

Nameservers
  • IP address
    216.239.34.107
    Host
    ns-cloud-b2.googledomains.com
  • IP address
    216.239.38.107
    Host
    ns-cloud-b4.googledomains.com
  • IP address
    216.239.32.107
    Host
    ns-cloud-b1.googledomains.com
  • IP address
    216.239.36.107
    Host
    ns-cloud-b3.googledomains.com
DNS zone
replit.app

Cookies

Cookies
  • Name
    GAESA

Location

IP address
34.117.33.233
ASN
396982
Organization
Google LLC
City
Kansas City
Country
US

TLS certificate

Issuer
Google Trust Services / WR3
Subject
replit.app

DNS records

A
  • 34.117.33.233

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Header value
max-age=63072000; includeSubDomains
Observation
HSTS header does not contain the preload directive.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
max-age=63072000; includeSubDomains
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
34.117.33.233
IP version
4

Redirects

Redirect chain
  • https://server-security-page--suebru300.replit.app

Page links

External link addresses
  • https://passwordreset.microsoftonline.com/
  • https://www.microsoft.com/en-US/servicesagreement/
  • https://privacy.microsoft.com/en-US/privacystatement
External links
3
Internal links
1

HTTP headers

Response headers
Server
Google Frontend
Content-type
text/html; charset=utf-8
Strict-transport-security
max-age=63072000; includeSubDomains
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "server-security-page--suebru300.replit.app"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Crawler rules
{
    "agents": [
        "*"
    ],
    "present": true
}
Page title and metadata
{
    "title": "Sign in to your account",
    "robots": "none"
}
Trackers
{
    "requests": 8,
    "trackers": [
        {
            "name": "jQuery",
            "company": "JS Foundation",
            "country": "US",
            "category": "Hosting",
            "requests": 1
        }
    ]
}
Forms and mixed content
{
    "no_sri": [
        "https://replit-cdn.com/replit-pill/replit-pill.global.js",
        "https://code.jquery.com/jquery-3.1.1.min.js"
    ],
    "third_party_scripts": 2
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 133,
        "tls": 20,
        "wait": 60,
        "connect": 100,
        "download": 17
    },
    "response_ms": 330
}
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
    ]
}
Carbon
{
    "bytes": 114160,
    "co2_grams": 0.0042,
    "cleaner_than": 19
}
Dns server
{
    "ns": [
        {
            "ip": "216.239.34.107",
            "host": "ns-cloud-b2.googledomains.com"
        },
        {
            "ip": "216.239.38.107",
            "host": "ns-cloud-b4.googledomains.com"
        },
        {
            "ip": "216.239.32.107",
            "host": "ns-cloud-b1.googledomains.com"
        },
        {
            "ip": "216.239.36.107",
            "host": "ns-cloud-b3.googledomains.com"
        }
    ],
    "zone": "replit.app"
}
Cookies
{
    "cookies": [
        {
            "name": "GAESA"
        }
    ]
}
Location
{
    "ip": "34.117.33.233",
    "asn": "396982",
    "org": "Google LLC",
    "city": "Kansas City",
    "country": "US"
}
Ssl
{
    "issuer": "Google Trust Services / WR3",
    "subject": "replit.app"
}
DNS records
{
    "A": [
        "34.117.33.233"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "header": "max-age=63072000; includeSubDomains",
    "message": "HSTS header does not contain the preload directive."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": "max-age=63072000; includeSubDomains",
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "34.117.33.233",
    "family": 4
}
Redirects
{
    "chain": [
        "https://server-security-page--suebru300.replit.app"
    ]
}
Page links
{
    "external": [
        "https://passwordreset.microsoftonline.com/",
        "https://www.microsoft.com/en-US/servicesagreement/",
        "https://privacy.microsoft.com/en-US/privacystatement"
    ],
    "external_count": 3,
    "internal_count": 1
}
HTTP headers
{
    "headers": {
        "server": "Google Frontend",
        "content-type": "text/html; charset=utf-8",
        "strict-transport-security": "max-age=63072000; includeSubDomains"
    }
}
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Phishing Phishing (detected)

Questions about server-security-page--suebru300.replit.app

Is server-security-page--suebru300.replit.app legit?

PhishDestroy records the captured sign-in page at server-security-page--suebru300.replit.app, whose HTML title reads "Sign in to your account".

Is server-security-page--suebru300.replit.app safe to connect a wallet?

This report does not record which wallet requests server-security-page--suebru300.replit.app 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 server-security-page--suebru300.replit.app?

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)
Observed page title
Sign in to your account
TLS Certificate
Issued by Google Trust Services / WR3 · stored validity ends in 86 days

Domain details

Domain
IP Reputation United States34.117.33.233 abuse score 60/100 15 reports Fraud OrdersFTP Brute-ForcePhishingFraud VoIPEmail SpamPort ScanHackingSpoofingBrute-ForceBad Web BotWeb App Attack checked Nov 1, 2026 last reported
Registrar (base domain) Replit
Abuse contactabuse@replit.com
Registration (base domain)replit.app · Created Apr 16, 2021 — Expires Apr 16, 2034
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedOct 31, 2026
DOM Analysisanalyzed Nov 1, 2026score 0/100
Submitted URLhttp://server-security-page--suebru300.replit.app/
Favicon Hash
ICANN OVERSIGHT Registration: replit.app

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

For the registrable domain replit.app behind this subdomain, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.

Accreditation is a contract, not a safety certification.

RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.

Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
United States34.117.33.233
Network ASN
AS396982
Organization
Google LLC
Observed location
United StatesKansas City, US
Server header
Google Frontend

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WR3
Valid from
2026-10-28 04:51:45
Valid until
2027-01-26 05:47:40
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint9d66dbe59ada0a41e27e591854785cf65280827d651cc4eab47765cf85053250
Certificate names · 2 SANs
  • replit.app
  • *.replit.app

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

Technologies · 7 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

14 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection
alphaMountain.ai
BitDefender
DNS8
ESET
Emsisoft
Fortinet
G-Data
Gridinsoft
Kaspersky
LevelBlue
Netcraft
SOCRadar
URLQuery
VIPRE
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of server-security-page--suebru300.replit.app · checked Oct 31, 2026

96
Good
Performance
FCP
2.27 s
First Contentful Paint
LCP
2.27 s
Largest Contentful Paint
CLS
0.011
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
2.27 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details1

Availability observations

Last reachable observation

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: 9 SHA-256 hashes: 9 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-31 22:49 UTC.

Open this scan on URLScan 01a19425-af07-7087-b761-a1809f4abfe6 ↗

Stored observation history1

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

  1. Domain monitor · First collection record

    Reachable

All retained availability observations2

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_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-10-31 23:49:03.000000
    Evidence SHA-256
    bf1c9cd63bfa2c78b4ab7369a4454453798a9bee0094cf94a3a9016a60fef1dc
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 23:49:03
    Evidence reason
  2. 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-10-31 23:49:03.000000
    Evidence SHA-256
    bf1c9cd63bfa2c78b4ab7369a4454453798a9bee0094cf94a3a9016a60fef1dc
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 23:49:03
    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
    server-security-page--suebru300.replit.app detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Cloudflare Radar: Malicious · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 7 of 7
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan classified the page as malicious · Score: 100
  • 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: 14/92
  • Cloudflare Radar: Malicious
    Cloudflare Radar classified this domain as phishing, Phishing (detected)
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
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

4 entries
  1. Cloudflare Radar

    Phishing

    View source
  2. Added to PhishDestroy

    server-security-page--suebru300.replit.app

    View source
  3. URLScan

    Page captured

    View source
  4. VirusTotal

    14/92 engine detections

    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.

Check for cloaking

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

server-security-page--suebru300.replit.app

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 server-security-page--suebru300.replit.app)
  • 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/server-security-page--suebru300.replit.app"
  title="PhishDestroy threat report for server-security-page--suebru300.replit.app"
  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>