Skip to security report
Analytics Dashboard
Domain security report
invoice.payment.gl favicon

invoice.payment.gl

“Blocked”

Threat verdict
CriticalDomain Appeal
Assessment sources

Assessment based on the stored source evidence below. Review sources →

Availability Last known active Latest stored reachability observation Observed · HTTP probe
Risk signals
VirusTotal detections: 16/89 Spamhaus DBL: DBL_PHISH Automated brand label: Reddit
Sep 9, 2026 Reddit CDN
API
Registrar
NiceNIC
Resolved IP
52.14.24.255
Registered
Mar 8, 2026
2 sources
The capture source is temporarily unavailable.
1 / 2
Source
Primary capture
Collected · UTC
Open capture
This domain has been flagged as malicious
Security engines reporting a detection: 16. Exercise extreme caution — do not enter credentials or personal information.
Additional indicators at a glance
Spamhaus DBL
DBL_PHISH
VirusTotal
VirusTotal
16 det.
URLScan
URLScan
Report ↗
TLS Certificate
Expired or unverified
Age
7 mo
Observed status
Last known active 302
PhishDestroy
DestroyList
Listed

Source evidence

8 · sources

These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.

VirusTotal

16 / 89

Report
Interpretation & limits

Engine detections from this stored analysis. Vendors and collection times may differ from other sources.

Spamhaus DBL

DBL_PHISH

Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

OTX

no community references

Report
Interpretation & limits

Community publication references, not a vendor verdict or evidence of a common operator.

CF Radar

provider verdict: clean

Observation time not recorded
Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

URLScan capture

stored report

View stored capture ↗
Report
Interpretation & limits

A preserved page image documents what the collector received; a capture is not a safety verdict.

URLScan verdict

Analysis completed

Report
Interpretation & limits

This is the recorded automated analysis. Completion alone is not a safety verdict.

Google Safe Browsing

Checked; no threat flag recorded

Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Public blocklists

0 external matches

Details
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Network Security Intelligence Registrar context
Registrar context NiceNIC
Stored registration data identifies NICENIC INTERNATIONAL GROUP CO., LIMITED (IANA 3765) as the registrar. PhishDestroy maintains separate NiceNIC abuse-report research; registrar association is contextual and is not an independent detection for this domain.
NiceNIC Verdict Full Investigation

Evidence Summary

Critical
VirusTotal
16/89
URLScan
Stored capture

Stored narrative · generated . Provider checks below retain their own observation dates.

Assessment

On 2026-10-01, invoice.payment.gl returned an HTTP 302 status in a recorded HTTP check. The same domain was first observed on 2026-09-09, according to the recorded first observation date.

Read the full analysis3

Recorded Evidence

The PhishDestroy internal listing for invoice.payment.gl was recorded as true, and the earliest observation of this domain is dated 2026-09-09. A VirusTotal check on 2026-09-18 recorded 16 detections across 89 scanners, while the SSL certificate scan on 2026-09-10 identified Let's Encrypt / YE2 as the issuer. The HTTP check on 2026-10-01 returned status 302, and the PageSpeed check on 2026-09-09 produced a performance score of 14.

Interpretation

The PhishDestroy listing and the VirusTotal result were recorded on different dates, so their observations describe separate points in time rather than one combined snapshot. Because the HTTP check on 2026-10-01 and the SSL scan on 2026-09-10 also fall on different dates, a reader can compare the recorded values but cannot treat them as simultaneous measurements. The PageSpeed score from 2026-09-09 adds another dated observation that should be read alongside, not merged with, the later records.

Recommended Actions

Anyone reviewing invoice.payment.gl should retain the dated records from PhishDestroy, VirusTotal, and the HTTP check so later observations can be compared against them. Avoid submitting passwords, payment details, or other sensitive information while examining invoice.payment.gl, and note that the 2026-10-01 HTTP 302 response does not by itself establish current availability. If further checks are made, record their dates and values separately to preserve a clear timeline.

Data coverage & collection18 · datasets with records / 13 · not recorded

What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.

Recorded dataPartial recordUTC
VirusTotal
16 / 89 · engine detections
URLScan analysis
Automated verdict retained
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
0 · community references
External blocklists
0 · external matches
Cloudflare Radar
cleanCollection time not recorded
Spamhaus DBL
DBL_PHISH
Domain registration
NICENIC INTERNATIONAL GROUP CO., LIMITEDCollection time not recorded
Network & DNS
52.14.24.255 · 2 · nameserversCollection time not recorded
TLS certificate
Let's Encrypt / YE2
Page captures
2 · retained captures
Page analysis
1 · automated brand labels
Observed indicators
0 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
PageSpeed performance
14/100 · mobile performance
Availability history
39 · stored state changes
Source observation history
1 · stored source events
IP reputation
Network-level observations
Not recorded in this report 13

These checks have no retained result. This does not mean they passed or that a scan is running.

  • URLQuery
  • PhishStats
  • DNS security filters
  • Gridinsoft
  • Scamadviser
  • HTML archives
  • Site configuration files
  • Response records
  • Recorded subdomains
  • Lookalike relationships
  • Community reports
  • Chainabuse records
  • Wayback archive
Download the dated observations and supporting metadata.
Blocklist records0 · external source matches

Public Blocklist Status

Domain, network & archiveNICENIC INTERNATIONAL GROUP CO., LIMITED · 52.14.24.255 · DNS, TLS and retained responses

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Context Fastly shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar (base domain) NiceNIC RU(RU) PhishDestroy Investigation
Abuse contactabuse@nicenic.net
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for payment.gl →
Registration (base domain)payment.gl · Created Mar 8, 2026 (221d) — Expires Mar 8, 2027
HTTP Status302 Found (Temporary)
Technical detailsProvenance & timestamps
First DetectedSep 9, 2026
DOM Analysisanalyzed Sep 10, 2026score 88/1001 brand signal
Submitted URLhttp://invoice.payment.gl/
Favicon Hash

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
52.14.24.255
Network ASN
AS16509
Organization
AWS EC2 (us-east-2)
Observed location
Columbus, US
Server header
snooserv

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • donald.ns.cloudflare.com
  • margaret.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-09-16 00:39:26
Valid until
2026-12-15 00:39:25
Hostname coverage
Hostname coverage not recorded
Validity
Within stored validity dates
Collection time
2026-10-11 01:02:45 UTC
Collection source
PhishDestroy collector
Certificate fingerprint600c8093b50024b941b8d2dd1718e41cfb411758f5674650a672077cf2bf1125

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

viewdns.info · 52.14.24.255rapiddns.io

Latest Classified Outcome 2026-10-15 10:59:25 UTC

Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-10-15 10:59:25 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-15 10:59:25 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 · 7 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

16 / 89 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 16 detections
ADMINUSLabs
BitDefender
Chong Lua Dao
CyRadar
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
Seclookup
SOCRadar
Sophos
VIPRE
Webroot
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of invoice.payment.gl · checked Sep 9, 2026

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

Availability observations

Last reachable observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Detection & evasion checksStored browser and crawler observations
Detection-evasion analysis

Cloaking and traffic-distribution check

Not yet scanned No crawler-versus-browser difference has been recorded yet

Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.

Stored cloaking flag
Not yet scanned
Last cloaking scan
Server header seen by scanner
Caddy

Scanner note: redirect: raw=redirect_302; http=302; via=https_proxy; location=https://redd.it/1x452h5; server=Caddy

Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Waiting
Timeline & responseCollection history, report status and investigation channels

Forensic History & Detection Timeline

ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
  1. Threat First Observed 2026-09-09 19:06:38 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as alive pointing to IP 52.14.24.255.
Stored observation history40

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

    Unknown→redirected

    http_redirect

  2. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  3. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  4. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  5. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

Earlier observations 35
  1. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  2. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  3. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  4. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  5. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  6. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  7. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  8. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  9. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  10. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  11. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  12. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  13. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  14. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  15. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  16. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  17. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  18. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  19. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  20. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  21. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  22. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  23. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  24. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  25. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  26. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  27. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  28. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  29. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  30. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  31. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  32. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  33. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  34. Availability monitor · Recorded state

    redirected

    http_redirect

  35. Availability monitor · First collection record

    Reachable

Threat Response Pipeline

Discovery
Analysis
Monitoring

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

Threat Ingested
invoice.payment.gl detected and queued for full analysis
Sep 9, 2026
Spamhaus DBL
Spamhaus DBL recorded DBL_PHISH
Oct 10, 2026
URLScan.io Capture
Stored URLScan report with capture artifacts
Sep 9, 2026
Cloudflare Radar Report
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
VirusTotal
16/89 recorded on VirusTotal
Sep 18, 2026
Registrar Context: NiceNIC
Separate registrar research is available. Registrar association is contextual and is not scored as an independent detection.
Brand Impersonation
Impersonation of Reddit
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
Sep 9, 2026
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results.
Oct 16, 2026
DestroyList Published
Listed in the public PhishDestroy/DestroyList repository
Sep 9, 2026
Monitoring Continues
The domain remains reachable or access-restricted; future checks may update this observation.
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
Related infrastructureShared hosting, registrar records and related domains
Evidence & investigation toolsOriginal reports, independent checks and evidence links

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 16 det. ChainPatrol URLQuery SSL Labs Hostname coverage not recorded 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 & reportingRecovery steps, reporting contacts and complaint drafts

Were You Affected by This Site?

3 evidence signal groups linked 0 reports recorded Last known active
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.

Europol
Find the official reporting channel for your EU country
National police directory
PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
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 →

Report to Your Local Authorities

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

97-country directory

Template-based draft · optional AI wording assistance requires separate consent

Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself

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

Live Threat Feed Appeal This Listing
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/invoice.payment.gl"
  title="PhishDestroy threat report for invoice.payment.gl"
  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>