Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Security engines reporting a detection: 3. Public blocklists reporting a match: 1. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
usps.eemerg.dev favicon

usps.eemerg.dev

In short

usps.eemerg.dev is a USPS impersonation page detected by PhishDestroy on 2026-10-27.

“USPS Tow Service — Dispatch”

Review the evidence
Resolved IP
United States5.161.51.236Hetzner Online GmbH
First observed
Oct 28, 2026
PhishDestroy assessment High
69/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 3/92 Stored blocklist matches: 1 Automated brand label: USPS
VirusTotal
3 / 92
engine detections ·
Blocklist matches
1
Phishunt
Cloudflare Radar
Phishing
Page captures
3
open gallery
Oct 28, 2026
X Telegram API

Analysis

Domain summary

usps.eemerg.dev is a USPS impersonation page detected by PhishDestroy on 2026-10-27. Risk: high (69/100). Status: Last known active. Hosting: Hetzner Online GmbH. VirusTotal: 3/92 engines flag it. Do not enter credentials or connect a wallet.

High
Status
Last known active
VirusTotal
3 / 92
Blocklist matches
1
Hosting
United States5.161.51.236Hetzner Online GmbH
Page captures
3
Page captures Source results

PhishDestroy threat report

Overview

PhishDestroy’s intake AI flagged the site as malicious, citing brand impersonation and a credential‑login prompt. The domain was first seen by PhishDestroy on 2026-10-28. A fetch on that date returned HTTP 200 and the recorded title “USPS Tow Service — Dispatch”.

How the scam works

The typical phishing flow presents a trusted brand’s look‑and‑feel, then asks the visitor to enter a username and password that are harvested for credential theft. Attackers rely on the brand’s reputation to trick users into disclosing login details that can be used to compromise real USPS accounts.

Evidence

VirusTotal scan on 2026-10-27 reported 3 malicious detections out of 92 engines, with CRDF, CyRadar and SOCRadar labeling it phishing. Google Safe Browsing check on 2026-10-28 did not flag the URL. urlscan.io capture on 2026-10-27 gave an overall clean verdict but its machine‑learning engine assigned a malicious score of 46. Cloudflare Radar scan on 2026-10-28 marked the URL as malicious phishing, and the external blocklist Phishunt also listed the domain while OTX showed zero pulses.

Infrastructure

The recorded IP was 5.161.51.236, belonging to Hetzner Online GmbH, ASN 213230, located in the United States. TLS was issued by Let’s Encrypt on 2026-09-13 and is valid until 2026-12-12. The domain was registered 43 days before the first sighting and uses the nameservers ns67.domaincontrol.com and ns68.domaincontrol.com.

What to do

Anyone who entered USPS credentials on this page should change their password immediately and enable two‑factor authentication on the official USPS portal. Organizations should block the domain and monitor outbound connections to 5.161.51.236 for any signs of credential harvesting.

Useful links

urlscan.io scan and screenshotCloudflare Radar reportStored capture screenshotCloudflare Radar screenshot (2026-10-27T23:51:42Z)VirusTotal reportGoogle Safe Browsing statusArchived copyReport phishing to GoogleSite owner? Request a review
Source evidenceVirusTotal 3 / 92 7 sources

VirusTotal

3 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
53
Malicious
3
Suspicious
0
Undetected
36

Vendor labels

CRDF
malicious
CyRadar
phishing
SOCRadar
phishing

Reputation score

0

Categories

Google
government
Webroot
Phishing and Other Frauds
alphaMountain.ai
Phishing (alphaMountain.ai)

Registrar

GoDaddy.com, LLC

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    600
    Type
    A
    Value
    5.161.51.236

DNS records observed

JARM fingerprint

40d40d40d00000000043d40d40d43da936ab0256fab25eca082941d14e3ece

Certificate

Subject alternative names
  • usps.eemerg.dev
Issuer
Let's Encrypt / YE2
Serial
5b9966503f14232b800a79827123717a56d
SHA-256
6dd867fd6bd7b820e840054d65b81c300c31fa615dc94ac87557ff6f675e43e9
Subject
usps.eemerg.dev
Valid until
Valid from

Registration record

Registrar
GoDaddy.com, LLC
Registrar IANA ID
146
Registrar URL
https://www.godaddy.com/
Registered
Updated
Expires
Status
  • clientDeleteProhibited
  • clientRenewProhibited
  • clientTransferProhibited
  • clientUpdateProhibited
Nameservers
  • ns67.domaincontrol.com
  • ns68.domaincontrol.com
DNSSEC
unsigned
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 53,
    "malicious": 3,
    "suspicious": 0,
    "undetected": 36
}
Vendor labels
{
    "CRDF": "malicious",
    "CyRadar": "phishing",
    "SOCRadar": "phishing"
}
Reputation
0
Categories
{
    "Google": "government",
    "Webroot": "Phishing and Other Frauds",
    "alphaMountain.ai": "Phishing (alphaMountain.ai)"
}
Registrar
GoDaddy.com, LLC
Created
2020-11-18T22:08:57Z
Expires
2023-11-18T22:08:57Z
Updated
2023-07-19T03:24:32Z
First seen
2026-09-13T22:23:55Z
DNS records
[
    {
        "ttl": 600,
        "type": "A",
        "value": "5.161.51.236"
    }
]
Dns at
2026-10-27T17:17:57Z
Jarm
40d40d40d00000000043d40d40d43da936ab0256fab25eca082941d14e3ece
Certificate
{
    "san": [
        "usps.eemerg.dev"
    ],
    "issuer": "Let's Encrypt / YE2",
    "serial": "5b9966503f14232b800a79827123717a56d",
    "sha256": "6dd867fd6bd7b820e840054d65b81c300c31fa615dc94ac87557ff6f675e43e9",
    "subject": "usps.eemerg.dev",
    "valid_to": "2026-12-12T20:56:10Z",
    "valid_from": "2026-09-13T20:56:11Z"
}
Registration record
{
    "registrar": "GoDaddy.com, LLC",
    "registrar_iana_id": "146",
    "registrar_url": "https://www.godaddy.com/",
    "created": "2020-11-18T22:08:57Z",
    "updated": "2023-07-19T03:24:32Z",
    "expires": "2023-11-18T22:08:57Z",
    "status": [
        "clientDeleteProhibited",
        "clientRenewProhibited",
        "clientTransferProhibited",
        "clientUpdateProhibited"
    ],
    "nameservers": [
        "ns67.domaincontrol.com",
        "ns68.domaincontrol.com"
    ],
    "dnssec": "unsigned"
}
Separate source record · 3 malicious + 0 suspicious / 92 · 2026-10-27 17:12:30 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-27T17:12:30Z
fetched_at
2026-10-27T23:50:34Z
stats
{"timeout":0,"harmless":53,"malicious":3,"suspicious":0,"undetected":36}

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Report ID

33096786-ed07-43b1-8371-e08acfdef3ea

Final URL

https://usps.eemerg.dev/

HTTP response

200

Navigation history

  • URL
    https://usps.eemerg.dev/
    Status
    200

DOM structure hash

faa80c6548ae5310375f4966cddf9d6c757b051306cecbd6a5b5528770a71bc3

Document hash

5f3469eb329891288b6ae5df2a609cc869d8f9e411137e126f9fdd03f121da68

URL risk categories

  • Phishing

Domain risk categories

  • Phishing
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    usps.eemerg.dev
    Type
    A
    Value
    5.161.51.236

DNSSEC valid

No

IP address

127.0.1.2

Verdict

Tags
  • phishing
Malicious
Yes
Categories
  • phishing

Registration record

Registrar
GoDaddy.com, LLC
Registered
Updated
Expires
Nameservers
  • ns67.domaincontrol.com
  • ns68.domaincontrol.com
Original source fields · JSON
Uuid
33096786-ed07-43b1-8371-e08acfdef3ea
Final url
https://usps.eemerg.dev/
Status
200
History
[
    {
        "url": "https://usps.eemerg.dev/",
        "status": 200
    }
]
DOM structure hash
faa80c6548ae5310375f4966cddf9d6c757b051306cecbd6a5b5528770a71bc3
Document hash
5f3469eb329891288b6ae5df2a609cc869d8f9e411137e126f9fdd03f121da68
Url risks
[
    "Phishing"
]
Domain risks
[
    "Phishing",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "usps.eemerg.dev",
        "type": "A",
        "value": "5.161.51.236"
    }
]
Dnssec valid
false
Ip
127.0.1.2
Verdict
{
    "tags": [
        "phishing"
    ],
    "malicious": true,
    "categories": [
        "phishing"
    ]
}
Registration record
{
    "registrar": "GoDaddy.com, LLC",
    "created": "2020-11-18T22:08:57Z",
    "updated": "2026-01-02T22:08:57Z",
    "expires": "2026-11-18T22:08:57Z",
    "nameservers": [
        "ns67.domaincontrol.com",
        "ns68.domaincontrol.com"
    ]
}
Separate stored summary: Not recorded · observation date not recorded

This summary differs from the dated scan above. It is retained for provenance and does not override the selected source observation.

verdict
null
categories
[]
observed_at
null
source_path
phishdestroy.technologies.cf_radar
scope
Separate stored summary; an absent observation date is not evidence of a clean scan.

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

URLScan

Page capture

Open report
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
01a17e6a-e721-72ba-ba93-3cff3258e09d
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

PhishDestroy DOM

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

Open report
Separate monitor score · 25 / 100 · 2026-10-28T00:05:09Z

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
25
analyzed_at
2026-10-28T00:05:09Z
source_timestamp
2026-10-28 01:05:09
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
usps.eemerg.dev — USPS Phishing Site
ai_description
PhishDestroy flagged usps.eemerg.dev (page title “USPS Tow Service — Dispatch”) as a malicious site that impersonates USPS and solicits login credentials.
ai_generated_at
2026-10-27T23:52:39Z
ai_generated_by
threat-v3-groq
interpretation
Narrative generation metadata, separate from provider 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: 21 fields

CAA records

Domain
usps.eemerg.dev

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Web archive observations

Last observation
First observation
Recorded changes
0
Archived days
1
Average page size, bytes
1058

Page title and metadata

Page title
USPS Tow Service — Dispatch

Trackers

Requests
5
Observed services
  • Name
    Google Fonts
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    1
  • Name
    Google Static
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    1

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
70
TLS
175
Waiting
187
Connection
202
Download
0
Response time, ms
634

TLS connection

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

Ports

Open ports
  • 22
  • 80
  • 443

Carbon estimate

Bytes
748
CO₂, grams
0
Cleaner than, %
95

DNS servers

Nameservers
  • IP address
    173.201.71.44
    Host
    ns68.domaincontrol.com
  • IP address
    97.74.103.44
    Host
    ns67.domaincontrol.com
DNS zone
eemerg.dev

Location

IP address
5.161.51.236
ASN
213230
Organization
Hetzner Online GmbH
City
Washington
Country
US

TLS certificate

Issuer
Let's Encrypt / YE2
Subject
usps.eemerg.dev

DNS records

A
  • 5.161.51.236

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
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
5.161.51.236
IP version
4

Redirects

Redirect chain
  • https://usps.eemerg.dev

Subdomains

Count
53
Subdomains
  • appc.eemerg.dev
  • appwrite-c0wkowcs40ck0084o8gc44sk.eemerg.dev
  • appwrite-c80sw8wkgw44woccg0s8cooo.eemerg.dev
  • appwrite-e4c4kgowo0088400gkgwkcc0.eemerg.dev
  • appwrite-e8gwogcck4kkc4w0wook0cww.eemerg.dev
  • appwrite-jwkcww0ggk8so4c4ccswosgk.eemerg.dev
  • appwrite-n8wg0k44wc40gok0wo00kks0.eemerg.dev
  • appwrite-q000w4cwg44cgcckg80sksko.eemerg.dev
  • appwrite-q4oso08skoo448o4084ks888.eemerg.dev
  • appwrite-testb.eemerg.dev
  • appwrite-u40oks4sckkk0kg080s8wswc.eemerg.dev
  • appwrite-v4gogw04cgo0swsoo404oscg.eemerg.dev
  • appwrite-yg0gwwcwow8wo8wok0g8ww8c.eemerg.dev
  • backend-c8g80sgwscskkgkook80ckg8.eemerg.dev
  • backend-hkos4cwkskowc80cc0o4c8c0.eemerg.dev
  • backend-kscgw8o0w0kk4co4gs8gcc4o.eemerg.dev
  • backend-no4cos8gkocc8sggk0oo8k40.eemerg.dev
  • backend-q8osgo4oksoskwgkocoskggo.eemerg.dev
  • backend-wk44kk0gc4gksoo8kw4cgggg.eemerg.dev
  • convertx-ko4o0844gc4sc8ssk0c44k40.eemerg.dev
  • convex-c8g80sgwscskkgkook80ckg8.eemerg.dev
  • convex-hkos4cwkskowc80cc0o4c8c0.eemerg.dev
  • convex-kscgw8o0w0kk4co4gs8gcc4o.eemerg.dev
  • convex-q8osgo4oksoskwgkocoskggo.eemerg.dev
  • convex-wk44kk0gc4gksoo8kw4cgggg.eemerg.dev
  • dashbc.eemerg.dev
  • demo-usps.eemerg.dev
  • dkc00k0kgw4gs0c0wggcsgoc.eemerg.dev
  • edgesvr.eemerg.dev
  • ek08o04ckc8kskcwsw4sookw.eemerg.dev
  • fleet.eemerg.dev
  • gitea-lg8kcswog4ww8sw04s8sow8s.eemerg.dev
  • gitea.eemerg.dev
  • gitlab.eemerg.dev
  • mediamtx.eemerg.dev
  • mixpost-h8gcs04woo4wkg0kkgw48444.eemerg.dev
  • n8n-u4sso0ggswk0swgoko0csc4k.eemerg.dev
  • pb-demo-usps.eemerg.dev
  • pb-hotmess-dev.eemerg.dev
  • pb-pdfex-dev.eemerg.dev
  • pb-prod-usps.eemerg.dev
  • pb-usps.eemerg.dev
  • pb-yomo-dev.eemerg.dev
  • pb23-pdfex.eemerg.dev
  • pocketbase-test.eemerg.dev
  • pocketbase-wkgw404s4g44ckgggkgo4kgw.eemerg.dev
  • s5uzjkq2h4hd3k7t3hfizbpm.eemerg.dev
  • supabasekong-ao8sossk84gksgwog8kwg4gw.eemerg.dev
  • usps-pb-prod.eemerg.dev
  • usps.eemerg.dev

HTTP headers

Response headers
Content-type
text/html
Original source fields · JSON
Caa records
{
    "domain": "usps.eemerg.dev"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-10-27T23:47:26Z",
    "first": "2026-10-27T23:47:26Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 1058
}
Page title and metadata
{
    "title": "USPS Tow Service — Dispatch"
}
Trackers
{
    "requests": 5,
    "trackers": [
        {
            "name": "Google Fonts",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 1
        },
        {
            "name": "Google Static",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 1
        }
    ]
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 70,
        "tls": 175,
        "wait": 187,
        "connect": 202,
        "download": 0
    },
    "response_ms": 634
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_128_GCM_SHA256",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        22,
        80,
        443
    ]
}
Carbon
{
    "bytes": 748,
    "co2_grams": 0,
    "cleaner_than": 95
}
Dns server
{
    "ns": [
        {
            "ip": "173.201.71.44",
            "host": "ns68.domaincontrol.com"
        },
        {
            "ip": "97.74.103.44",
            "host": "ns67.domaincontrol.com"
        }
    ],
    "zone": "eemerg.dev"
}
Location
{
    "ip": "5.161.51.236",
    "asn": "213230",
    "org": "Hetzner Online GmbH",
    "city": "Washington",
    "country": "US"
}
Ssl
{
    "issuer": "Let's Encrypt / YE2",
    "subject": "usps.eemerg.dev"
}
DNS records
{
    "A": [
        "5.161.51.236"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "5.161.51.236",
    "family": 4
}
Redirects
{
    "chain": [
        "https://usps.eemerg.dev"
    ]
}
Subdomains
{
    "count": 53,
    "subdomains": [
        "appc.eemerg.dev",
        "appwrite-c0wkowcs40ck0084o8gc44sk.eemerg.dev",
        "appwrite-c80sw8wkgw44woccg0s8cooo.eemerg.dev",
        "appwrite-e4c4kgowo0088400gkgwkcc0.eemerg.dev",
        "appwrite-e8gwogcck4kkc4w0wook0cww.eemerg.dev",
        "appwrite-jwkcww0ggk8so4c4ccswosgk.eemerg.dev",
        "appwrite-n8wg0k44wc40gok0wo00kks0.eemerg.dev",
        "appwrite-q000w4cwg44cgcckg80sksko.eemerg.dev",
        "appwrite-q4oso08skoo448o4084ks888.eemerg.dev",
        "appwrite-testb.eemerg.dev",
        "appwrite-u40oks4sckkk0kg080s8wswc.eemerg.dev",
        "appwrite-v4gogw04cgo0swsoo404oscg.eemerg.dev",
        "appwrite-yg0gwwcwow8wo8wok0g8ww8c.eemerg.dev",
        "backend-c8g80sgwscskkgkook80ckg8.eemerg.dev",
        "backend-hkos4cwkskowc80cc0o4c8c0.eemerg.dev",
        "backend-kscgw8o0w0kk4co4gs8gcc4o.eemerg.dev",
        "backend-no4cos8gkocc8sggk0oo8k40.eemerg.dev",
        "backend-q8osgo4oksoskwgkocoskggo.eemerg.dev",
        "backend-wk44kk0gc4gksoo8kw4cgggg.eemerg.dev",
        "convertx-ko4o0844gc4sc8ssk0c44k40.eemerg.dev",
        "convex-c8g80sgwscskkgkook80ckg8.eemerg.dev",
        "convex-hkos4cwkskowc80cc0o4c8c0.eemerg.dev",
        "convex-kscgw8o0w0kk4co4gs8gcc4o.eemerg.dev",
        "convex-q8osgo4oksoskwgkocoskggo.eemerg.dev",
        "convex-wk44kk0gc4gksoo8kw4cgggg.eemerg.dev",
        "dashbc.eemerg.dev",
        "demo-usps.eemerg.dev",
        "dkc00k0kgw4gs0c0wggcsgoc.eemerg.dev",
        "edgesvr.eemerg.dev",
        "ek08o04ckc8kskcwsw4sookw.eemerg.dev",
        "fleet.eemerg.dev",
        "gitea-lg8kcswog4ww8sw04s8sow8s.eemerg.dev",
        "gitea.eemerg.dev",
        "gitlab.eemerg.dev",
        "mediamtx.eemerg.dev",
        "mixpost-h8gcs04woo4wkg0kkgw48444.eemerg.dev",
        "n8n-u4sso0ggswk0swgoko0csc4k.eemerg.dev",
        "pb-demo-usps.eemerg.dev",
        "pb-hotmess-dev.eemerg.dev",
        "pb-pdfex-dev.eemerg.dev",
        "pb-prod-usps.eemerg.dev",
        "pb-usps.eemerg.dev",
        "pb-yomo-dev.eemerg.dev",
        "pb23-pdfex.eemerg.dev",
        "pocketbase-test.eemerg.dev",
        "pocketbase-wkgw404s4g44ckgggkgo4kgw.eemerg.dev",
        "s5uzjkq2h4hd3k7t3hfizbpm.eemerg.dev",
        "supabasekong-ao8sossk84gksgwog8kwg4gw.eemerg.dev",
        "usps-pb-prod.eemerg.dev",
        "usps.eemerg.dev"
    ]
}
HTTP headers
{
    "headers": {
        "content-type": "text/html"
    }
}

Questions about usps.eemerg.dev

Is usps.eemerg.dev legit?

No. PhishDestroy classifies usps.eemerg.dev as a USPS impersonation page (risk: high, 69/100); it was first detected on 2026-10-27. VirusTotal: 3/92 engines flag it. Treat the site as unsafe.

Is usps.eemerg.dev safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on usps.eemerg.dev. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used usps.eemerg.dev?

Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy · Phishunt · no match in the other 10 2
PhishDestroy PhishDestroy list View source
Phishunt Listed View source

Checked, no match

Last checked

Stored Capture · 3 captures

Primary capture 1 / 3
SourcePrimary capture
Recorded
StateStored capture
Position1 / 3
Open capture Wayback Download
All capture links and hashes (3)
usps.eemerg.dev: USPS impersonation — Flagged by Phishunt, 3/92 VirusTotal engines. PhishDestroy risk score 69/100 (high).
Social preview card usps.eemerg.dev: USPS impersonation — Flagged by Phishunt, 3/92 VirusTotal engines. PhishDestroy risk score 69/100 (high). v ab3bb7d444e5

Domain details

Domain
Registrar (base domain) Unknown
Abuse contactabuse@hetzner.com
Hosting abuse contact abuse@hetzner.com Hetzner Online GmbH · AS213230
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 28, 2026
DOM Analysisanalyzed Oct 28, 2026score 25/1001 brand signal
Submitted URLhttps://usps.eemerg.dev/login
Observed page title
USPS Tow Service — Dispatch
Automated brand references
Usps
TLS Certificate
Issued by Let's Encrypt / YE2 · stored validity ends in 45 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
United States5.161.51.236
Network ASN
AS213230
Organization
Hetzner Online GmbH
Observed location
United StatesWashington, US

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-09-13 20:56:11
Valid until
2026-12-12 20:56:10
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint6dd867fd6bd7b820e840054d65b81c300c31fa615dc94ac87557ff6f675e43e9
Certificate names · 1 SAN
  • usps.eemerg.dev

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

viewdns.info · 5.161.51.236rapiddns.io
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

3 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection
CRDF
CyRadar
SOCRadar

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of usps.eemerg.dev · checked Oct 28, 2026

82
Needs Work
Performance
FCP
3.6 s
First Contentful Paint
LCP
3.62 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
3.6 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 200
Requested URL: https://usps.eemerg.dev/login
USPS Tow Service — Dispatch
Response
HTTP 200
HTML body
748 B
Compressed
458 B
Links
0 internal · 0 external
Selected response headers
Content-Encoding: gzip
Content-Type: text/html
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Favicon fingerprint: 5f3469eb329891288b6ae5df2a609cc869d8f9e411137e126f9fdd03f121da68
Saved response-header values · 8
Alt-Svc
h3=":443"; ma=2592000
Content-Encoding
gzip
Content-Length
461
Content-Type
text/html
Date
Tue, 27 Oct 2026 23:46:53 GMT
Etag
"6ae023d9-2ec"
Last-Modified
Tue, 27 Oct 2026 04:08:57 GMT
Vary
Accept-Encoding

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

Archived
All retained availability observations1

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
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 00:53:38.556903
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

Threat Response Pipeline

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

Recorded events: 10. 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
    usps.eemerg.dev detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · Cloudflare Radar Report · Web Archive · VirusTotal · Blocklist Detection · Brand Impersonation · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 8 of 8
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • 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.
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • VirusTotal
    Detections recorded on VirusTotal: 3/92
  • Blocklist Detection
    Found in blocklists: Phishunt
  • Brand Impersonation
    Automated brand label: USPS
  • 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

5 entries
  1. URLScan

    Page captured

    View source
  2. Cloudflare Radar

    Phishing

    View source
  3. VirusTotal

    3/92 engine detections

    View source
  4. Wayback Machine

    Page archived

    View source
  5. Added to PhishDestroy

    usps.eemerg.dev

    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.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

Check for cloaking

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

usps.eemerg.dev

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 3 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid CF Radar Open report WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
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.

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

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
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.

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect

Report to Your Local Authorities

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

Even if funds were frozen, they cannot be recovered without an official police report or court order. Submitting a complaint is the only path to potential recovery.

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.

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

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including usps.eemerg.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

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

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.

Request a correction or appeal How PhishDestroy works
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/usps.eemerg.dev"
  title="PhishDestroy threat report for usps.eemerg.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>