Zum Sicherheitsbericht springen
Domänensicherheit und Bedrohungsinformationen
aynenoyle.com favicon

aynenoyle.com

“Parking Page”

Registrar
Spaceship
Resolved IP
34.216.117.25
Registered
03.08.2026
PhishDestroy assessment Kritisch
First observed Oct 22, 2026 06:31 UTC · PhishDestroy
VirusTotal-Erkennungen: 16/92 Automatische Markenkennung: Wordpress
OTX: 3 refs 22.10.2026 1 Report Sent
API
Diese Domain wurde als bösartig markiert.
Sicherheits-Engines melden eine Entdeckung: 16. Seien Sie äußerst vorsichtig – Geben Sie keine Anmeldeinformationen oder persönlichen Daten ein.
VirusTotal
engine detections
Google Safe Browsing
URLQuery
detections
OTX
community references
Page captures
open gallery
Domain age
Reports sent
view timeline
Berichtsübersicht

Wordpress-Imitation: aynenoyle.com — Nicht bestätigt. Zusammenfassung der Beweislage: VirusTotal 16/92 (ADMINUSLabs, alphaMountain.ai, BitDefender, Chong Lua…

Die ausführliche Analyse von PhishDestroy AI bleibt auf Englisch, damit der ursprüngliche forensische Bericht unverändert bleibt.

Source evidenceVirusTotal 16 / 92 · OTX 3 references 6 sources

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Analysis

Kritisch
VirusTotal
16 / 92
OTX
3 community refs
Page captures
5

PhishDestroy threat report

Overview

PhishDestroy added aynenoyle.com to its internal blocklist on 2026-10-22. The intake noted 13 malicious VirusTotal detections and a redirect to www.spaceship.com. A page fetch on the same day returned HTTP 200 with a client‑side redirect to the external site.

How the scam works

The detections suggest the domain may be used as a redirector, a common technique where a short‑lived domain forwards visitors to another site that hosts phishing or malicious content. No specific phishing page, credential‑stealing form, or malware payload was captured in the available scans, so the exact scam method remains unconfirmed.

Evidence

VirusTotal reported 13 malicious and 3 suspicious detections from 92 engines on 2026-10-22, with vendors such as ADMINUSLabs, BitDefender and Fortinet labeling it malicious or phishing. Google Safe Browsing checked the domain on 2026-10-22 and did not flag it. urlscan.io captured the site on 2026-08-05 with a clean verdict, while a later capture on 2026-10-22 showed 307 redirects between HTTP and HTTPS and engine scores marking it malicious (score 15). Cloudflare Radar scanned the domain on 2026-10-22 and classified it as malicious malware. OTX listed three pulses referencing the domain as of 2026-10-22. PhishDestroy’s internal blocklist marks it as blocked; external blocklists returned zero matches on the check date.

Infrastructure

The domain was registered on 2026-08-03 through Spaceship, Inc., with a clientTransferProhibited status and an expiration of 2027-08-03. DNS records include two A addresses (34.216.117.25 and 54.149.79.189) owned by Amazon.com, Inc., and DNSSEC is enabled. The TLS certificate is from Let’s Encrypt, valid from 2026-05-19 to 2026-08-17, and the nameservers are launch1.spaceship.net and launch2.spaceship.net.

What to do

Do not submit credentials, payment information, or crypto wallet details to aynenoyle.com or any page it redirects to. If you have entered such data, change passwords immediately and monitor associated accounts for unauthorized activity. Defenders should block the domain at network perimeters and review logs for any connections to these hosts.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

URLScan · 2026-10-22T06:37:14Z

Beobachtet: · Retrieved:

Uuid
01a16253-d939-7039-91d4-9ee87f9cc87d
Final url
http://aynenoyle.com/
Status
200
Redirects
[
    {
        "to": "https://aynenoyle.com/",
        "from": "http://aynenoyle.com/",
        "status": 307
    },
    {
        "to": "http://aynenoyle.com/",
        "from": "https://aynenoyle.com/",
        "status": 307
    }
]
Ip
54.149.79.189
Ptr
ec2-54-149-79-189.us-west-2.compute.amazonaws.com
Contacted IP addresses
[
    "54.149.79.189"
]
Asns
[
    "16509"
]
Countries
[
    "US"
]
Document hash
b855170518999450b40eb3685468416fcf5b011370c23eb2965a1d5c9ecf73be
Script hashes
[
    "400b88c144f3dc11f2b2ed22a155abc24348eebe41449f9edfc6e936d18e0b27"
]
Domain age days
2489
Apex age days
2489
Requests
6
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 15,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "openresty/1.31.1.1",
    "content-type": "text/html",
    "strict-transport-security": "max-age=31536000; includeSubDomains; preload",
    "content-security-policy": "frame-ancestors 'self'",
    "x-frame-options": "SAMEORIGIN",
    "x-content-type-options": "nosniff",
    "referrer-policy": "strict-origin-when-cross-origin"
}
Cloudflare Radar · 2026-10-22T06:39:26Z

Beobachtet: · Retrieved:

Uuid
0f850902-ac23-44c4-87ea-2b1d9cb9cb3c
Final url
https://aynenoyle.com/
History
[
    {
        "url": "https://aynenoyle.com/",
        "status": 0
    }
]
Domain risks
[
    "Malware",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "aynenoyle.com",
        "type": "A",
        "value": "54.149.79.189"
    },
    {
        "name": "aynenoyle.com",
        "type": "A",
        "value": "34.216.117.25"
    }
]
Dnssec valid
true
Verdict
{
    "tags": [
        "malware"
    ],
    "malicious": true,
    "categories": [
        "malware"
    ]
}
Registration record
{
    "registrar": "Spaceship, Inc.",
    "created": "2026-08-03T14:25:08Z",
    "updated": "2026-08-03T14:25:14Z",
    "expires": "2027-08-03T14:25:08Z",
    "nameservers": [
        "launch1.spaceship.net",
        "launch2.spaceship.net"
    ]
}
VirusTotal · 2026-10-18T17:46:02Z

Beobachtet: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 43,
    "malicious": 13,
    "suspicious": 3,
    "undetected": 33
}
Vendor labels
{
    "DNS8": "suspicious",
    "ESET": "suspicious",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "suspicious",
    "ADMINUSLabs": "malicious",
    "BitDefender": "phishing",
    "Chong Lua Dao": "malicious",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Popularity
{
    "Alexa": 632891,
    "Statvoo": 632891
}
Registrar
Spaceship, Inc.
Erstellt
2026-08-03T14:25:08Z
Expires
2027-08-03T14:25:08Z
Updated
2026-08-03T14:25:14Z
First seen
2024-05-29T16:05:31Z
DNS records
[
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "support.spaceship.com",
        "value": "launch1.spaceship.net"
    },
    {
        "ttl": 1800,
        "type": "NS",
        "value": "launch2.spaceship.net"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "34.216.117.25"
    },
    {
        "ttl": 1800,
        "type": "NS",
        "value": "launch1.spaceship.net"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "54.149.79.189"
    }
]
Dns at
2026-10-18T17:52:05Z
Jarm
28d28d28d00028d00042d42d000000e1ea2a807a629b496b664cf07ad7c08d
Certificate
{
    "san": [
        "aynenoyle.com"
    ],
    "issuer": "Let's Encrypt / E8",
    "serial": "526422b4653e429f5c2d3166e593f4ea318",
    "sha256": "325affc8c794a036b8346531cd735fbed3e2f42c4c1c4bc585477e3a47a06ff7",
    "subject": "aynenoyle.com",
    "valid_to": "2026-08-17T08:03:05Z",
    "valid_from": "2026-05-19T08:03:06Z"
}
Registration record
{
    "registrar": "Spaceship, Inc.",
    "registrar_iana_id": "3862",
    "registrar_url": "http://www.spaceship.com",
    "created": "2026-08-03T14:25:08Z",
    "updated": "2026-08-03T14:25:14Z",
    "expires": "2027-08-03T14:25:08Z",
    "status": [
        "clientTransferProhibited"
    ],
    "nameservers": [
        "launch1.spaceship.net",
        "launch2.spaceship.net"
    ],
    "dnssec": "signedDelegation"
}
Registry data
{
    "status": [
        "client transfer prohibited"
    ],
    "events": {
        "last changed": "2026-08-23T13:31:39Z",
        "registration": "2026-08-03T14:25:08Z",
        "registrar expiration": "2027-08-03T14:25:08Z",
        "last update of RDAP database": "2026-10-18T09:22:26Z"
    }
}
Website checks · 2026-10-22T06:41:09Z
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "aynenoyle.com"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Ports
{
    "open": [
        80
    ]
}
Dns server
{
    "ns": [
        {
            "ip": "162.159.27.32",
            "host": "launch2.spaceship.net"
        },
        {
            "ip": "162.159.26.38",
            "host": "launch1.spaceship.net"
        }
    ],
    "zone": "aynenoyle.com"
}
Location
{
    "ip": "34.216.117.25",
    "asn": "16509",
    "org": "Amazon.com, Inc.",
    "city": "Boardman",
    "country": "US"
}
DNS records
{
    "A": [
        "54.149.79.189",
        "34.216.117.25"
    ],
    "NS": [
        "launch1.spaceship.net",
        "launch2.spaceship.net"
    ],
    "SOA": "{\"nsname\": \"launch1.spaceship.net\", \"hostmaster\": \"support.spaceship.com\", \"serial\": 1785767114, \"refresh\": 43200, \"retry\": 3600, \"expire\": 604800, \"minttl\": 3600}"
}
Dnssec
{
    "ds": true,
    "rrsig": true,
    "dnskey": true
}
Get ip
{
    "ip": "54.149.79.189",
    "family": 4
}
Registration record
{
    "registrar": "Spaceship, Inc.",
    "created": "2026-08-03T14:25:08Z",
    "updated": "2026-08-03T14:25:14Z",
    "expires": "2027-08-03T14:25:08Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "launch1.spaceship.net",
        "launch2.spaceship.net"
    ]
}
Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Gespeicherte Aufnahme · 5 captures

Domain details

Domain
IP-Reputation abuse score 1/100 4 reports PhishingBad Web BotWeb App Attack checked 22.10.2026
Registrar Spaceship US(US)
Abuse-Kontaktabuse@spaceship.com
ICANN-RegistrierungsstelleICANN Lookup (RDAP) →
RegistrierungErstellt 03.08.2026 (79d · New) — Expires 03.08.2027
Technische DetailsProvenance & timestamps
Erstmals entdeckt22.10.2026
DOM Analysisanalyzed 22.10.2026score 10/1001 brand signal
Submitted URLhttp://aynenoyle.com/
Favicon Hash
Fall-ID
Observed page title
Parking Page
Automated brand references
Wordpress
TLS-Zertifikat
Ausgestellt von Let's Encrypt / E8

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
34.216.117.25
Network ASN
AS16509
Organization
Amazon.com, Inc.
Observed location
Boardman, US
Server header
openresty/1.31.1.1

Nameserver 2

  • launch1.spaceship.net
  • launch2.spaceship.net

Location describes the IP network.

TLS-Zertifikat

Issuer
Let's Encrypt / E8
Valid from
2026-05-19 08:03:06
Valid until
2026-08-17 08:03:05
Hostname coverage
Stored certificate expired or unverified
Validity
Stored certificate expired
Collection source
PhishDestroy collector
Certificate fingerprint325affc8c794a036b8346531cd735fbed3e2f42c4c1c4bc585477e3a47a06ff7
Certificate names · 1 SANs
  • aynenoyle.com

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

Recorded subdomains1

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • www.aynenoyle.comDomain record

The original observation time is not recorded for these hostnames.

Diese Domain melden Reichen Sie Beweismaterial ein und helfen Sie mit, andere zu schützen

VirusTotal-Analyse

16 / 92 Sicherheitsanbieter haben diese Domain markiert
View on VT
Last analyzed
ADMINUSLabs
alphaMountain.ai
BitDefender
Chong Lua Dao
DNS8
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Lionic
Seclookup
SOCRadar
Sophos
VIPRE
Webroot
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: http://aynenoyle.com/
Parking Page
Reaktion
HTTP 200
HTML body
37.8 KB
Compressed
9.2 KB
Links
0 internal · 0 external
Detected technologies
wordpress
Selected response headers
Server: openresty/1.31.1.1
Content-Type: text/html
Content-Encoding: gzip
Security headers present
Strict-Transport-SecurityContent-Security-PolicyX-Frame-OptionsX-Content-Type-OptionsX-XSS-ProtectionReferrer-Policy
HSTS: observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 17
Connection
keep-alive
Content-Encoding
gzip
Content-Security-Policy
frame-ancestors 'self'
Content-Type
text/html
Date
Thu, 22 Oct 2026 06:33:49 GMT
Etag
W/"d1f26a569f5ab57c1cdd7521672b95d7"
Last-Modified
Tue, 13 Oct 2026 11:14:05 GMT
Referrer-Policy
strict-origin-when-cross-origin
Server
openresty/1.31.1.1
Strict-Transport-Security
max-age=31536000; includeSubDomains; preload
Transfer-Encoding
chunked
Vary
Accept-Encoding
x-amz-version-id
Uai2TgSamz3aAs0Ty81nLUOlT0M_qrUL
X-Cache-Status
HIT
X-Content-Type-Options
nosniff
X-Frame-Options
SAMEORIGIN
X-XSS-Protection
1; mode=block

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

Registration & observation details1

Availability observations

Last reachable observation

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

Recorded activity

6 entries
  1. Abuse report sent

    PD-20261022-B30F7B

    abuse@spaceship.com
  2. AlienVault OTX

    3 community references

    View source
  3. URLScan

    Page captured

    View source
  4. Google Safe Browsing

    No threat flag

    View source
  5. VirusTotal

    16/92 engine detections

    View source
  6. Added to PhishDestroy

    aynenoyle.com

    View source

Check for cloaking

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

aynenoyle.com

Nachweise und externe Berichte

Momentaufnahme der übermittelten Beweise
Sent: Ledger records: 1 Case ID: PD-20261022-B30F7B Recipient: abuse@spaceship.com
Page title stored with report: Parking Page
PDF notice generated
Eingehende Analyse
Help & reporting

Wurden Sie von dieser Website betroffen?

6 evidence signal groups linked 1 stored notification records Nicht bestätigt
If credentials were compromised, report immediately. Do not engage with recovery scammers.

Wenn Sie Kontoanmeldeinformationen, persönliche oder Zahlungsinformationen eingegeben oder eine Datei von dieser Domain heruntergeladen haben, ergreifen Sie sofort Maßnahmen. Nachfolgend finden Sie Ressourcen, die Ihnen helfen, den Vorfall zu melden und sich zu schützen.

Official reporting routes

Vorsicht vor Betrügern, die mit der Rückforderung von Geldern locken! Kriminelle nehmen unter Umständen erneut Kontakt zu Opfern auf und geben dabei vor, Ermittler, Anwälte oder Beitreibungsbeamte zu sein. Zahlen Sie keine Vorabgebühren und geben Sie keine Anmeldeinformationen weiter. Erfahren Sie mehr über Betrug im Zusammenhang mit Wiederaufbaumaßnahmen →

Melden Sie sich bei Ihren örtlichen Behörden

Wählen Sie Ihr Land aus, um Offizielle Kontakte im Bereich Cyberkriminalität oder einen Beschwerdeentwurf erstellen → zu erhalten.

97-Länder-Verzeichnis

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

KI-gestützter Entwurf – Vorfalldetails werden vom KI-Anbieter verarbeitet · Überprüfen Sie es und reichen Sie es selbst ein
After a phishing incident

Empfehlungen und Ratschläge für Betroffene

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

Was soll ich sofort tun?

Dringend

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Alle Passwörter ändern — E-Mail, Exchange-Konten, alles, wofür dasselbe Passwort verwendet wird
  • 2FA aktivieren mit einer Authentifizierungs-App (nicht per SMS). Deaktivieren Sie die SMS-basierte Wiederherstellung
  • Karten einfrieren Falls Sie auf der Phishing-Seite Ihre Bankdaten eingegeben haben

Welche Informationen sollte ich für meinen Bericht sammeln?

FBI-Richtlinien

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.
  • Genaue Daten und Uhrzeiten — jeder Transaktion und des ersten Kontakts mit dem Betrüger
  • Screenshots — betrügerische Websites, Chat-Nachrichten, E-Mails, Wallet-Transaktionen, soziale Medien
  • Alle URLs und Domains die der Betrüger verwendet (einschließlich aynenoyle.com)
  • Kommunikation — E-Mails, SMS, Telefonnummern, Benutzernamen, die der Betrüger verwendet hat

Auch wenn dir nicht alle Details bekannt sind — trotzdem Anzeige erstatten. Auch unvollständige Informationen sind für die Ermittlungen hilfreich.

Wo soll ich den Betrugsfall melden?

  • FBI IC3 — Internet Crime Complaint Center (Meldestelle der US-Bundesbehörden)
  • Europol — Meldungen zu Cyberkriminalität in Europa (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Ortspolizei — sorgt für eine offizielle Dokumentation, auch wenn sie nicht sofort handeln können

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?

  • Gefälschte Websites — pixelgenaue Kopien legitimer Websites mit leicht abgeänderten Domains
  • Schweineschlachtung — über Wochen hinweg über Telegram, WhatsApp und Dating-Apps aufgebautes Vertrauen, dann wurde Geld gestohlen
  • Betrugsmaschen im Zusammenhang mit der Rückforderung von Geldern — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • Durch KI gestützte Betrugsmaschen — Deepfakes, automatisiertes Phishing und KI-generierte Websites, die es erschweren, Betrugsversuche zu erkennen

Wie kann ich mich in Zukunft schützen?

  • Offizielle Websites als Lesezeichen speichern — Klicken Sie niemals auf Links in E-Mails, Direktnachrichten oder Anzeigen
  • Domains überprüfen — nachsehen, ob PhishDestroy Bevor Sie Kontakt aufnehmen: Überprüfen Sie HTTPS, die Rechtschreibung und das Alter der Domain.
  • „Zu schön, um wahr zu sein“ = Betrug — garantierte Renditen, Prominente als Werbeträger, dringende Fristen

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Bleiben Sie auf dem Laufenden, bleiben Sie sicher

Beobachten Sie aktuelle Bedrohungen oder legen Sie Widerspruch gegen diesen Eintrag ein, wenn Sie der Meinung sind, dass es sich um einen Fehlalarm handelt

Echtzeit-Bedrohungsfeed Einspruch gegen diesen Eintrag einlegen
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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Diesen Bericht einbetten

Teilen Sie diese Bedrohungsinformationen auf Ihrer Website oder in Ihrem Blog

embed.html
<iframe
  src="https://phishdestroy.io/de/embed/domain/aynenoyle.com"
  title="PhishDestroy threat report for aynenoyle.com"
  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>