VirusTotal
16 / 91
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@dynadot.com.
The latest stored availability evidence still shows the domain reachable; 28 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
frontierintegritys.com — No verificado. Tipo de estafa: Impersonation. Resumen de las pruebas: VirusTotal 16/91 (alphaMountain.ai, BitDefender, CRDF, ESET, Emsisoft); URLQuery 6 alerts; Spamhaus DBL_MALWARE; CF Radar malicious; PhishDestroy score 100/100. Registrador: Dynadot.
El análisis detallado de PhishDestroy AI se mantiene en inglés para conservar el registro forense original.
16 / 91
6 threat-system alerts
Denunciarprovider verdict: malicious
DenunciarDBL_MALWARE
1 community reference
Denunciarinforme almacenado
Denunciar Análisis finalizado
Denunciar80/100
DenunciarChecked; no threat flag recorded
Denunciar| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| Quad9 DNS | frontierintegritys.com |
malicious | Sinkholed |
| DigiCert UltraDNS | frontierintegritys.com |
malicious | Sinkholed |
| CIRA Canadian Shield DNS | frontierintegritys.com |
malicious | Sinkholed |
| OpenDNS | frontierintegritys.com |
phishing | Phishing Block |
| DNS4EU | frontierintegritys.com |
malicious | Sinkholed |
| Cloudflare DNS | frontierintegritys.com |
malicious | Sinkholed |
Stored evidence for frontierintegritys.com: VirusTotal recorded 5 detections among 89 scanners on 2026-09-15. That ratio reproduces the stored check in its original units and is not converted into another measure. OpenPhish appear as named external blocklist observations for frontierintegritys.com. Each item in this report remains at the scope supplied by its dated source record.
VirusTotal records 5 detections among 89 scanners in the stored snapshot dated 2026-09-15. The numerator describes scanners that produced detections, while the denominator describes scanners included in that check. The reverse order would materially alter the stored result. The VirusTotal snapshot dated 2026-09-15 supplies no common rationale covering the included scanners, and this report adds none. A later VirusTotal snapshot may contain different values, so any comparison should preserve the exact ratio and date of each snapshot.
OpenPhish are recorded as named external blocklist observations for frontierintegritys.com in the snapshot dated 2026-09-15. The stored OpenPhish blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains frontierintegritys.com as a publisher record. That PhishDestroy record is counted separately from the OpenPhish external blocklist observations. This separation keeps the origin of every entry visible and prevents a single stored item from being counted again under another source label.
The record first observed frontierintegritys.com on 2026-09-15. The OpenPhish blocklist snapshot is dated 2026-09-15 and remains a separate event in the stored timeline. The registration date is separately recorded as 2026-08-18. Each timestamp qualifies only the adjacent observation in this timeline. Later collection results should be compared with these dated values without replacing the earlier snapshot.
For frontierintegritys.com, the registrar field records Dynadot Inc; this is kept as an exact source value. The source stores 172.67.196.238 as the observed address in this record. The registration date for frontierintegritys.com is recorded as 2026-08-18. These fields preserve registration, network, and certificate context stored in this record. The report preserves each label and number as a separate source value instead of combining them into an invented aggregate. Keeping the fields separate leaves every infrastructure value traceable to the record that supplied it.
The frontierintegritys.com record states that VirusTotal recorded 5 detections among 89 scanners on 2026-09-15. OpenPhish remain named blocklist observations from the snapshot dated 2026-09-15. PhishDestroy remains a separate publisher catalogue entry in the stored record. For frontierintegritys.com, the registrar field records Dynadot Inc; this remains separate from the other source fields. The observed address field in this record contains 172.67.196.238. The supported conclusion is bounded to the exact stored observations for frontierintegritys.com. Any statement beyond those source values would require additional dated material.
Avoid submitting sensitive information to frontierintegritys.com during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain frontierintegritys.com as an exact indicator and preserve relevant DNS, proxy, and endpoint records. Compare later VirusTotal snapshots and OpenPhish blocklist records with the dated values above instead of replacing them. Keep each later observation with its source date so changes remain visible during follow-up review. If a defensive rule is needed, keep its scope to frontierintegritys.com. The stored record does not justify extending that rule to 172.67.196.238 or to other infrastructure records.
Observaciones almacenadas de rastreadores frente a navegadores para este servidor, además de una comprobación en tiempo real de la huella digital para sistemas de distribución de tráfico al estilo Keitaro.
Nota del escáner: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='frontierintegritys.com', port=80): Max retries exceeded with url: / (Caused by NewConnecti
La reputación de Edge-IP no se atribuye a este dominio.
rafe.ns.cloudflare.comsterling.ns.cloudflare.comLocation describes the IP network.
654cd14723d02fbf318a23441ddefd4ba3055a23eccdf77ed621e929a52e6f3fSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
188.114.96.3. 12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
PD-20260915-845C4D Recipient: abuse@dynadot.com Registrar: Dynadot LLC / Dynadot Inc (United States) Policy Violations: Acceptable Use forbids illegal content; Spam & Abuse Policy prohibits phishing, fraud, malware; Dynadot may disable DNS and suspend domains Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
Si ingresó credenciales de cuenta, información personal o de pago, o descargó un archivo de este dominio, tome medidas inmediatas. A continuación encontrará recursos que le ayudarán a informar el incidente y protegerse.
Seleccione su país para obtener contactos oficiales de cibercrimen o crear un borrador de queja →.
Template-based draft · optional AI wording assistance requires separate consent
Análisis de amenazas utilizando listas de bloqueo almacenadas, WHOIS, DNS y evidencia de escaneo público
Escanear ahoraEnvía los dominios sospechosos a nuestra base de datos de amenazas: protege a la comunidad
DenunciarInformes de phishing recientes y cambios de disponibilidad observados
MonitorizarSupervisa las amenazas en tiempo real o impugna esta entrada si crees que se trata de un falso positivo.