Is pafinatunakota.org a scam site? Scam, spam & reviews
Scores & key points
Caution signals ⓘ
- [Medium] Newly registered domain.
- [Medium] No valid SSL/TLS certificate found.
- [Low] Without SPF/DMARC, email sender spoofing risk is increased.
Reputation
Review summary — pafinatunakota.org
Overall 42 (Suspicious site)Risk signals such as WHOIS privacy or missing security headers have been identified.
Strengths
- SPF configured
Weaknesses
- No valid SSL/TLS certificate
- HSTS not set
- CSP not set
- DMARC not configured
- Domain registered within the last 6 months
Detailed review — pafinatunakota.org
Domain review
Domain created: 2026-01-27T04:11:08Z (≈ 0m). Registrar: NameCheap, Inc.. Hosting / AS: DIGITALOCEAN-ASN - DigitalOcean, LLC, US — Singapore. Popularity: OPR 1.00/10. Reputation: GSB clean WebRisk clean. Email security: SPF On, DMARC None.
Shop / transaction review
No mixed content detected. No mixed content detected. Structured data: Organization Absent, contactPoint Absent. Hidden text ratio 0%.
Technical review
HSTS Off (preload: Unknown). Applies 0/6 security headers. DNSSEC Off. Email security: SPF On, DMARC None. MTA‑STS policy: None. TLS‑RPT Off. security.txt: not available. JS obfuscation score 0. Reputation: GSB clean, WebRisk clean → overall Good.
Explanation — strengths and stability
Age: about (≈ 0m) (created on 2026-01-27T04:11:08Z).
GSB clean
WebRisk clean
Email security: SPF On, DMARC None.
No mixed content detected.
Looking at operator information together with trust metrics helps you judge brand/merchant consistency and the likelihood of long‑term operation.
Checking payment page security (HTTPS enforcement, form target host consistency, script integrity) along with customer support and return policy gives a more accurate sense of real‑world trust.
In parallel, applying security headers, automated certificate renewal, email domain protection (DMARC/TLS‑RPT), and removing mixed content will improve overall reliability and delivery/search stability.
Explanation — risks and areas to improve
Without HSTS, downgrade and man‑in‑the‑middle attacks can weaken HTTPS enforcement. Enable HSTS and prepare for preload registration.
Missing key security headers leaves the site vulnerable to clickjacking, MIME sniffing, and data leakage.
Without DNSSEC, trust relies solely on parent name servers and DNS tampering risks can be higher in some environments.
If DMARC is absent or set to p=none, protection against sender spoofing is weak. Consider quarantine/reject policies.
Without MTA‑STS, SMTP TLS enforcement is weaker.
Without TLS‑RPT, it is harder to collect TLS failure signals and operational insight.
Without security.txt, the vulnerability disclosure channel is unclear and response may be delayed.
This analysis is an automated, data‑based opinion for reference only. Please verify the information yourself before paying or downloading anything.
About this report
- First analysis: -
- Last updated: 2026-02-21 08:26:29
Claim website ownership
Traffic signals
Security headers
- HSTS ⓘ
- Content‑Security‑Policy ⓘ
- X‑Content‑Type‑Options ⓘ
- X‑Frame‑Options ⓘ
- Referrer‑Policy ⓘ
- Permissions‑Policy ⓘ
add_header Strict-Transport-Security "max-age=15552000; includeSubDomains; preload" always;
add_header Content-Security-Policy "default-src 'self'; img-src 'self' data:; object-src 'none'; base-uri 'self'";
add_header X-Content-Type-Options "nosniff" always;
add_header X-Frame-Options "SAMEORIGIN" always;
add_header Referrer-Policy "strict-origin-when-cross-origin" always;
add_header Permissions-Policy "geolocation=(); microphone=(); camera=()" always;
v=DMARC1; p=quarantine; rua=mailto:dmarc@pafinatunakota.org; ruf=mailto:dmarc@pafinatunakota.org; fo=1
Domain lineage
-
2026-01-27Domain registered: 2026-01-27T04:11:08Z
Essentials
Threat insight
- New domain (< 6 months)
- Using invalid or expired SSL/TLS certificates triggers browser warnings and increases the risk of man‑in‑the‑middle attacks or confusion with phishing sites. Check certificate status regularly.
- Without HSTS, downgrade and man‑in‑the‑middle attacks can weaken HTTPS enforcement. Enable HSTS and prepare for preload registration.
- Missing key security headers leaves the site vulnerable to clickjacking, MIME sniffing, and data leakage.
- If DMARC is absent or set to p=none, protection against sender spoofing is weak. Consider quarantine/reject policies.
The risk score of this site is calculated by combining browser security headers, SSL status, mixed content, email domain protection (SPF/DMARC), redirect/obfuscation patterns, and the results of Google Safe Browsing and WebRisk. Strong signals indicate possible phishing or malware. Avoid any sensitive operations such as payments, logins, or entering wallet recovery phrases. Always verify that the operator information and contact methods match official sources, and that the domain in the address bar matches the legitimate site. Before entering payment or personal information, verify operator information (company/contact), HTTPS enforcement, DMARC/TLS‑RPT, and check for mixed content.
Deep scan (HTML / headers)
Before entering payment or personal information, verify the site operator/contact, HTTPS enforcement (HSTS), and the presence of DMARC and TLS‑RPT.
User scenarios
If you make a payment on this site
Entering card, bank or wallet details on this site is high risk. Only proceed after confirming the official domain via trusted channels. Mixed or non-encrypted (HTTP) resources or weak TLS can expose payment data or session tokens on some networks. Missing or weak DMARC lets attackers send spoofed payment emails. Type the domain manually instead of clicking links in unexpected messages.
If you log in or enter personal data
Entering passwords or sensitive identifiers on this site is high risk. Account takeover or identity abuse is more likely; verify the official domain or app first.
Server location ⓘ
History
Change ⓘ --Recently added sites
Reviews
Average - / total 0
Checksum e7930d3e2e02e3e6175f5dbb00c31dbc28c09ca834213dfb2481dca3c5837fa4