Website reputation report

finxture.dev

Last checked 1 month ago · Point-in-time assessment

68/100Technical Safety ScoreIndependent technical assessment, not a visitor rating
Would you recommend this page? No community votes yet 0/0 Your vote is for this page in this report only—not the entire website. No account required · One vote per browser.
Captured homepage of finxture.dev in the current scan
Website screenshot from the current report

Share report

Automated technical analysis and moderated visitor experiences are different sources. A score is not a recommendation or a guarantee of safety.

● Evidence is limited

What is this website?

Finxture is built by one engineer who has integrated payment providers at job after job. Why it was started, what it is trying to become, and what it actually does today.

Website descriptions use observed page content and publisher statements; they are not verified business claims. How sources are used.

No listed local patterns observedHomepage-only analysis is not a malware clearance. Read the scope and findings below.

68/100Safety Score
75%Evidence Confidence
Trust Radar evidence profile Eight evidence dimensions from zero to one hundred. Exact values surround the chart. Threat Intelligence55 Domain History39 Infrastructure92 Website Security95 Security Hygiene55 Transparency61 Reputation50 Operational Stability85
Trust RadarEight observed factors. Select one to inspect its evidence.

How to read this report

Safety Score evaluates observed signals. Evidence Confidence measures how complete, direct, fresh, and consistent those signals are.

No automated scan can guarantee that a website is safe.

Current report context

What changed since the last scan

  • No earlier report to compare
What this scan could verify · 6 observed, 0 unavailable
DNS observed
Registration lookup observed
Network observed
TLS observed
Website response observed
Website content observed

Unavailable and unperformed checks are not clean results. The detailed evidence below remains the source for each conclusion.

Report an inaccuracy in this report →

Independent evidence brief

What we observed about finxture.dev

Updated Oct 11, 2026

The latest scan examined 9 public pages on finxture.dev. Website descriptions below come from the site itself. Registration, connection and threat findings were checked separately.

Purpose and visible content

On its About page, the site says: Finxture is built by one engineer who has integrated payment providers at job after job. Why it was started, what it is trying to…

Registrar and domain history

Registered on Jul 19, 2026. Registrar: CloudFlare, Inc..

Recorded expiry date: Jul 19, 2027. Registry data can change.

Connection and hosting evidence

The checked homepage returned HTTP 200 in about 1000 ms.

A valid TLS certificate was observed, expiring Dec 15, 2026.

Threat checks and score context

External malware-provider coverage was unavailable. The report does not treat this missing check as a clean result.

Safety Score: 68/100. Evidence Confidence: 75%. These measure different things.

Community reviews of finxture.dev

No approved reviews yet ☆☆☆☆☆

Visitor experiences are separate from the independent technical Safety Score.

Visitor opinions remain separate from the technical Safety Score.

Public content profile

Pages reviewed on finxture.dev

9 of up to 10 pages

We sampled public pages from this website to understand its subject and contact paths. The titles and short descriptions below come from the website itself. They are not endorsements or independent safety findings.

Finxture — test payment webhooks and failure scenarios on localhostFinxture is a free Chrome extension that runs deterministic payment webhook scenarios — duplicate delivery, out-of-order events, retries after non-2xx — against your localhost. No About Finxture — why it exists and who builds itFinxture is built by one engineer who has integrated payment providers at job after job. Why it was started, what it is trying to become, and what it actually does today. Guides — FinxturePractical, step-by-step guides for testing payment integrations on localhost. Payment scenarios — FinxtureEvery payment scenario Finxture can run against localhost — duplicates, retries, declines — and where each one is explained. Payment concepts — FinxtureProvider-neutral definitions of the payment concepts the scenarios and guides build on. How a Finxture scenario is builtOne worked example — payment-succeeds — through the three layers a Finxture scenario is made of: the real-world event, the Stripe rendering of it, and the choice of how delivery ge Stripe test mode, the Stripe CLI, and stripe-mock: what each is for — FinxtureAn honest comparison of Stripe test mode, the Stripe CLI's listen and trigger, stripe-mock, and Finxture — what each one is genuinely good at, where each one stops, and the two cas A successful payment sends two webhooks, not one — FinxtureWhat the two events of a successful two-stage payment actually assert, why the baseline run is the one to keep as a fixture, and how to check that your handler tells an authorizati Duplicate webhook delivery in payment integrations — FinxtureWhy payment providers deliver the same webhook event more than once, what it breaks, how to deduplicate correctly, and how to prove your handler survives it.

Public page evidence

Topics and keywords observed on finxture.dev

12 phrases

These phrases were extracted locally from sampled public page metadata. They are observations, not search-volume or ranking estimates.

paymentTitle, H1, Meta description8 sampled pages
scenariosTitle, H1, Meta description3 sampled pages
testTitle, H1, Meta description2 sampled pages
deliveryTitle, H1, Meta description3 sampled pages
localhostTitle, Meta description3 sampled pages
is builtTitle, H1, Meta description2 sampled pages
payment integrationsTitle, H1, Meta description2 sampled pages
eachTitle, H1, Meta description2 sampled pages
guidesTitle, H1, Meta description2 sampled pages
scenarioTitle, H1, Meta description2 sampled pages
stripeTitle, H1, Meta description2 sampled pages
webhookTitle, H1, Meta description2 sampled pages

Recorded evidence

Key findings for finxture.dev

These observations describe the recorded scan, not the website today. Open each evidence section to inspect its scope and limitations.

HTTP 200 at scan time

A server response was recorded. An HTTP response alone does not verify the business or the safety of its content.

View response evidence

Valid certificate observed

The certificate was valid when checked. Encryption protects the connection; it does not establish that the operator is trustworthy.

View TLS evidence

External checks unavailable

No usable external provider verdict is stored. Local checks are shown separately; missing external coverage is not a clean result.

View provider results

Fully explainable

Why this score?

Versioned weights
Threat IntelligenceWeight 25%
55/100

Threat providers were unavailable. The neutral uncertainty baseline is not a clean verdict.

Domain HistoryWeight 10%
39/100

Domain registration age and expiry were checked.

InfrastructureWeight 10%
92/100

Observed DNS records and network address were checked.

Website SecurityWeight 15%
95/100

Observed certificate validity and TLS protocol were checked.

Security HygieneWeight 15%
55/100

Observed security header values were checked for basic protective settings. Empty values, disabled HSTS and unrecognized values receive no credit. This is not a complete browser-policy validation.

TransparencyWeight 5%
61/100

Observed site metadata and About page were checked. Publisher-supplied details are not independently verified.

ReputationWeight 5%
50/100

Popularity is weak context, not proof of safety. Unranked sites use a neutral baseline.

Operational StabilityWeight 15%
85/100

Observed HTTP status and final connection scheme were checked.

Server-side analysis

Automated security checks

Local antivirus and phishing checks

ClamAV · homepage HTMLNo signature match in the sampled HTML
Engine version1.5.4
Signature database date (UTC)2026-10-10T06:24:04+00:00
HTML bytes submitted28,663
Phishing.Database · exact hostnameNot listed in this snapshot
Feed downloaded (UTC)2026-10-11T06:00:17+00:00
Hosts in local snapshot386,082

Sampled scripts and pages

Resource analysis incomplete

2 resources checked · 0 script links observed on the homepage. Partial resource coverage.

ClamAV inspects the fetched homepage HTML on our server. New scans also sample up to four linked scripts and two collected internal pages, with size and time limits. Scripts are not executed. Other downloads, private server files and logged-in pages remain outside this check. A signature match needs investigation and can be a false positive. No match is not a whole-site safety guarantee.

Exact hostname lookup uses a downloaded Phishing.Database snapshot. It does not send this domain to an external lookup API or mark sibling subdomains as harmful. Not listed does not mean safe. Snapshot age is download age, not proof that every entry was recently revalidated.

Homepage HTML only · Eight local rule families · local-security-v2

Checks use the fetched page and redirect chain. Scripts are not executed, forms are not submitted, and linked files are not downloaded. This is not a malware clearance.

Page resource inventory

Linked scripts0
Inline scripts1
Embedded frames0
External script hosts0

Counts describe the sampled HTML, not every resource loaded by the browser. External resources are common and are not automatically harmful.

No listed local patterns observed. The limited rule set cannot detect every threat or behavior.

External threat intelligence

Provider coverageNot checked

Local checks do not query external reputation databases. An unavailable check is never a clean result.

Registration

Domain information

Public RDAP observation
Canonical domainfinxture.dev
RegistrarCloudFlare, Inc.
RegisteredJul 19, 2026
Domain age4 months
ExpiresJul 19, 2027
Registry statusesclient transfer prohibited
Report statePublished

Infrastructure

Network & hosting

Observed endpoint, not legal location
IP address104.21.30.120
Autonomous systemUnavailable
Network organizationUnavailable
Observed countryUnavailable
CDNCloudflare
Web application firewallNot detected

At a glance

Infrastructure summary

Observed during this scan

A compact view of the connection, DNS and security surface. These observations describe what the scanner could verify at scan time and do not prove ownership or ongoing availability.

HTTP response200 · https://finxture.dev/
Endpoint104.21.30.120
NetworkUnavailable
CDN and WAFCloudflare · Not detected
DNS surface11 records · 2 nameservers · 3 mail exchangers
Protection signals2 security headers · 2 technologies · DNSSEC unknown

Page telemetry

Observed page statistics

Safe metadata only

These counters describe the fetched response and sampled HTML. Script counts describe references in the markup, not a complete browser network log. Cookie counts cover observed response headers.

Response size28,663 bytes
HTTP check duration1,000 ms
Cookies observedUnavailable
Script resources0 · 0 external hosts
Frames and sampled checks0 frames · 2 resources checked

Encrypted transport

TLS certificate

Valid when observed
StatusValid when observed
ProtocolTLSv1.3
IssuercountryName=US, organizationName=Google Trust Services, commonName=WE1
Valid fromSep 16, 2026
Valid untilDec 15, 2026
Certificate namesfinxture.dev

Resolution

DNS footprint

DNSKEY status unknown

DNSKEY presence does not verify the DNSSEC signature chain. Missing records can mean no record was returned or the lookup was unavailable.

A104.21.30.120TTL —
A172.67.172.229TTL —
AAAA2606:4700:3032::ac43:ace5TTL —
AAAA2606:4700:3037::6815:1e78TTL —
NSelijah.ns.cloudflare.comTTL —
NSraphaela.ns.cloudflare.comTTL —
MX37 route1.mx.cloudflare.netTTL —
MX43 route3.mx.cloudflare.netTTL —
MX91 route2.mx.cloudflare.netTTL —
TXTgoogle-site-verification=m--vkc8TbkPPG8JuCsqF6UdVl_XH1qHV83tUUgkn7RQTTL —
TXTv=spf1 include:_spf.mx.cloudflare.net ~allTTL —

DNS observations · no external lookup API

Domain email protection

Exact-host SPF and DMARC observations help the owner investigate email impersonation risks. They are separate from website malware checks and do not change the Safety Score.

SPFPolicy record observed, not fully validated
DMARCNo matching record returned for this exact hostname

What to do next

Review the records with your mail administrator. Inventory legitimate senders and test SPF and DKIM alignment before enforcing a stricter DMARC policy. Fix duplicate records and investigate overly permissive SPF rules.

This bounded check does not send email, probe SMTP, evaluate recursive SPF includes, verify DKIM signatures or apply organizational-domain DMARC inheritance. A missing subdomain record does not prove that no inherited protection exists. A DNS timeout is unknown, not an absent record. A policy record is not proof that messages authenticate successfully.

Responsible disclosure

security.txt

RFC 9116 observation

No readable security.txt file was observed at the standard locations. This is informational and is not evidence of malware.

Browser protections

Security headers

2 observed
referrer-policypresent strict-origin-when-cross-origin
x-content-type-optionspresent nosniff

Response headers

Cookie protections

Passive observation

No Set-Cookie header was observed on the sampled homepage response. Other pages may set cookies separately.

Detected stack

Technologies

Bootstrap 80% Cloudflare 98%

Versions are shown only when publicly exposed by the page or response headers. An observed version is not, by itself, proof of a vulnerability.

JavaScript library advisories

JavaScript advisory analysis could not be completed or no eligible script files were sampled. No clean result is implied.

About this website

What the site says about itself

Finxture is built by one engineer who has integrated payment providers at job after job. Why it was started, what it is trying to become, and what it actually does today.

View the site's About page ↗

This is a short excerpt of publisher supplied information, not our own review. The independent safety findings are shown separately.

Structured facts

Website identity & response

Public page metadata
Page titleFinxture — test payment webhooks and failure scenarios on localhost
First headingTest the payment failures your provider's sandbox can't.
DescriptionFinxture is a free Chrome extension that runs deterministic payment webhook scenarios — duplicate delivery, out-of-order events, retries after non-2xx — against your localhost. No magic amounts, no ngrok.
Canonical URLhttps://finxture.dev/
Final URLhttps://finxture.dev/
HTTP response200 · text/html; charset=utf-8 · 1000 ms
Languageen
Structured typesFAQPage · Question
Page page detectedhttps://finxture.dev/guides/About page detectedhttps://finxture.dev/about/
Page about1100% evidence confidence
Page languageen100% evidence confidence
Page page1100% evidence confidence
Security txt statusmissing100% evidence confidence
Local headers cors credentials with wildcardNo value recorded100% evidence confidence
Dns consistency cname presentNo value recorded100% evidence confidence
Dns consistency dnssec stateunavailable100% evidence confidence
Dns consistency mail route count3100% evidence confidence
Dns consistency nameserver count2100% evidence confidence
Dns consistency record count11100% evidence confidence
Dns consistency address count4100% evidence confidence
Local headers cors present1100% evidence confidence
Local headers cors wildcard origin1100% evidence confidence
Local headers csp presentNo value recorded100% evidence confidence
Local headers hsts presentNo value recorded100% evidence confidence
Local headers permissions policy presentNo value recorded100% evidence confidence

Connection path

Redirect chain

0 recorded hops

No redirect hop was recorded for the sampled homepage.

Report history

Understand changes between completed checks

Reports record observations at the time of each scan. Repeat checks require a manual request and verification; viewing this page never starts another scan.

Explore website owner tools

Compared with the previous scan

What changed

A comparison will appear after the next completed scan.

Explainable matching

Digital fingerprint

fingerprint-v1
steady-harbor-ring-176

Comparable components help find technically related websites. A match does not prove common ownership.

DnsHashed private comparison value
TechnologiesHashed private comparison value

Material changes only

Change history

Show change history

No meaningful changes recorded yet.

Website icon for finxture.dev

Visual evidence

Website screenshot

Screenshot of finxture.dev
Captured once in an isolated browser during this scan. Visual tint is an interface overlay. The original evidence is not duplicated.

For site owners

Show your verified trust report

Place this lightweight badge in your footer to show visitors an independent, dated WebsiteVirusScanner report. It can increase visitor confidence, but it never changes or guarantees the score.

Choose a badge style
Preview on your site
WebsiteVirusScanner trust badge preview

Use the current report link so visitors can verify the evidence. A badge is a transparency signal, not a paid ranking boost.

Questions about finxture.dev

FAQ

Still have questions? Contact us →
Is finxture.dev safe to visit?

The latest Safety Score is 68/100 with 75% Evidence Confidence. This is a point-in-time assessment of observed technical signals, not a guarantee. Check the exact address and avoid entering payment details if anything looks unusual.

Did the scan detect malware on finxture.dev?

ClamAV found no signature match in the sampled homepage HTML. External scripts, downloads and private server files were not checked. This is not a whole-site malware clearance.

When was finxture.dev registered?

The public registry record shows Jul 19, 2026. Registration details may be privacy-protected or updated later.

Did finxture.dev have a valid TLS certificate?

The scanner observed a valid TLS certificate using TLSv1.3. A valid certificate alone does not establish that the site is safe.

How does finxture.dev describe itself?

The website's About page describes its purpose in the report above. This is publisher-supplied information and is separate from independent security findings.

Can a paid listing change this website's score?

No. Premium placement and owner-supplied pages are labelled separately. Technical evidence, the Safety Score and moderation decisions remain independent.

Share your experience with finxture.dev

Community reviews are moderated and remain separate from the technical Safety Score.

Write review →