Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Security engines reporting a detection: 14. Public blocklists reporting a match: 1. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
ticket-att.com favicon

ticket-att.com

In short

ticket-att.com is a phishing page detected by PhishDestroy on 2026-10-26.

“ticket-att.com”

Review the evidence
Registrar
Key-Systems
Resolved IP
216.245.184.250
PhishDestroy assessment Critical
100/100
Evidence score
First observed Oct 26, 2026 11:40 UTC · PhishDestroy
Risk signals
VirusTotal detections: 14/92 Stored blocklist matches: 1
VirusTotal
14 / 92
engine detections ·
OTX
3
community references
Cloudflare Radar
Phishing
Page captures
8
open gallery
OTX: 3 refs Oct 26, 2026
X Telegram API

Analysis

Domain summary

ticket-att.com is a phishing page detected by PhishDestroy on 2026-10-26. Risk: critical (100/100). Registrar: Key-Systems. Hosting: BL Networks. VirusTotal: 14/92 engines flag it. Do not enter credentials or connect a wallet.

Critical
VirusTotal
14 / 92
OTX
3 community refs
Page captures
8
Page captures Source results Registration record

PhishDestroy threat report

Overview

PhishDestroy listed ticket-att.com as a suspicious domain based on automated analysis. The site was first seen by PhishDestroy on 2026-10-26. A urlscan capture on that date recorded a page under /wireless/step02.php that was classified as malicious and associated with the AT&T brand. Google Safe Browsing did not flag the domain on the same day.

How the scam works

The assessment reflects that the domain matches patterns often used in deceptive pages that reference well‑known brands, but the captured page did not reveal any specific credential‑collection behavior.

Evidence

VirusTotal reported fourteen malicious detections out of ninety‑two engines on 2026-10-26, with vendors such as BitDefender, Fortinet, G‑Data and Kaspersky labeling the domain as phishing or malicious. urlscan recorded a 200 response for the page under /wireless/step02.php on 2026-10-26 and gave a malicious verdict with a score of 100, categorising it as phishing and linking it to the AT&T brand. OpenPhish includes the domain on its blocklist, and OTX lists three pulses mentioning it. PhishDestroy’s internal blocklist also marks the domain as malicious. Google Safe Browsing returned no flag on 2026-10-26.

Infrastructure

The domain was registered on 2026-10-24 through Key‑Systems GmbH, with the creation record dated 2026-10-25. The recorded IP was 216.245.184.250, associated with BL Networks in the United States. The TLS certificate issued by Let’s Encrypt on 2026-10-24 was valid until 2027-01-22 and covered ticket-att.com and www.ticket-att.com. Nameservers were dns1.monsterdns.net, dns2.monsterdns.net and dns3.monsterdns.net.

What to do

If users entered AT&T credentials on this site, they should change those passwords immediately and enable two‑factor authentication on their AT&T accounts. Organizations should block ticket-att.com in network filters, monitor DNS logs for queries to the domain, and review authentication logs for any suspicious activity. Simply visiting the site does not prove compromise, but any credential submission warrants remediation.

Useful links

urlscan.io scan and screenshotCloudflare Radar reportStored capture screenshotCloudflare Radar screenshot (2026-10-26T11:42:32Z)URLScan screenshot (2026-10-25T14:25:17Z)URLScan capture reportURLScan screenshot (2026-10-26T01:05:03Z)URLScan capture reportURLScan screenshot (2026-10-26T04:31:27Z)URLScan capture reportURLScan screenshot (2026-10-26T04:49:40Z)URLScan capture reportURLScan screenshot (2026-10-26T06:06:54Z)URLScan capture reportVirusTotal reportGoogle Safe Browsing statusReport phishing to GoogleSite owner? Request a review
Source evidenceVirusTotal 14 / 92 · OTX 3 references 8 sources

VirusTotal

14 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 15 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
47
Malicious
14
Suspicious
0
Undetected
31

Vendor labels

CRDF
malicious
Ermes
phishing
G-Data
phishing
Lionic
phishing
Sophos
phishing
Webroot
malicious
Emsisoft
phishing
Fortinet
phishing
Netcraft
malicious
Kaspersky
phishing
MalwareURL
phishing
BitDefender
phishing
alphaMountain.ai
phishing
Forcepoint ThreatSeeker
phishing

Reputation score

0

Categories

Google
telecommunications
Sophos
phishing and fraud
Webroot
Phishing and Other Frauds
Forcepoint ThreatSeeker
phishing and other frauds

Registrar

Key-Systems GmbH

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    21600
    Type
    NS
    Value
    ns3.rrpproxy.net
  • TTL, seconds
    21600
    Type
    SOA
    Responsible mailbox
    tech.rrpproxy.net
    Value
    ns1.rrpproxy.net
  • TTL, seconds
    21600
    Type
    NS
    Value
    ns1.rrpproxy.net
  • TTL, seconds
    21600
    Type
    NS
    Value
    ns2.rrpproxy.net
  • TTL, seconds
    2542
    Type
    A
    Value
    216.245.184.250

DNS records observed

JARM fingerprint

27d40d40d00040d00042d43d0000003d25bc6207ca8acd9652e99aa3724a08

Certificate

Subject alternative names
  • ticket-att.com
  • www.ticket-att.com
Issuer
Let's Encrypt / YE2
Serial
68c6dbdc920bd8a363dce5ce37fee5a3218
SHA-256
a6432c2b1838fd231e1269bd6ae456823c5c7c1534ebdccd7c33d3cab48a9342
Subject
ticket-att.com
Valid until
Valid from

Registration record

Registrar
Key-Systems GmbH
Registrar IANA ID
269
Registrar URL
http://www.key-systems.net
Registered
Updated
Expires
Status
  • clientTransferProhibited
Nameservers
  • dns1.monsterdns.net
  • dns2.monsterdns.net
  • dns3.monsterdns.net
DNSSEC
unsigned

Registry data (RDAP)

Status
  • client transfer prohibited
Registry events
Expiration
Last changed
Registration
Registrar expiration
Last RDAP database update
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 47,
    "malicious": 14,
    "suspicious": 0,
    "undetected": 31
}
Vendor labels
{
    "CRDF": "malicious",
    "Ermes": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "Webroot": "malicious",
    "Emsisoft": "phishing",
    "Fortinet": "phishing",
    "Netcraft": "malicious",
    "Kaspersky": "phishing",
    "MalwareURL": "phishing",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Categories
{
    "Google": "telecommunications",
    "Sophos": "phishing and fraud",
    "Webroot": "Phishing and Other Frauds",
    "Forcepoint ThreatSeeker": "phishing and other frauds"
}
Registrar
Key-Systems GmbH
Created
2026-10-24T22:13:39Z
Expires
2027-10-24T22:13:39Z
Updated
2026-10-24T22:15:47Z
First seen
2024-03-04T15:23:17Z
DNS records
[
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns3.rrpproxy.net"
    },
    {
        "ttl": 21600,
        "type": "SOA",
        "rname": "tech.rrpproxy.net",
        "value": "ns1.rrpproxy.net"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns1.rrpproxy.net"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns2.rrpproxy.net"
    },
    {
        "ttl": 2542,
        "type": "A",
        "value": "216.245.184.250"
    }
]
Dns at
2026-10-25T21:27:29Z
Jarm
27d40d40d00040d00042d43d0000003d25bc6207ca8acd9652e99aa3724a08
Certificate
{
    "san": [
        "ticket-att.com",
        "www.ticket-att.com"
    ],
    "issuer": "Let's Encrypt / YE2",
    "serial": "68c6dbdc920bd8a363dce5ce37fee5a3218",
    "sha256": "a6432c2b1838fd231e1269bd6ae456823c5c7c1534ebdccd7c33d3cab48a9342",
    "subject": "ticket-att.com",
    "valid_to": "2027-01-22T21:21:44Z",
    "valid_from": "2026-10-24T21:21:45Z"
}
Registration record
{
    "registrar": "Key-Systems GmbH",
    "registrar_iana_id": "269",
    "registrar_url": "http://www.key-systems.net",
    "created": "2026-10-24T22:13:39Z",
    "updated": "2026-10-24T22:15:47Z",
    "expires": "2027-10-24T22:13:39Z",
    "status": [
        "clientTransferProhibited"
    ],
    "nameservers": [
        "dns1.monsterdns.net",
        "dns2.monsterdns.net",
        "dns3.monsterdns.net"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "client transfer prohibited"
    ],
    "events": {
        "expiration": "2027-10-24T22:13:39Z",
        "last changed": "2026-10-24T22:15:47Z",
        "registration": "2026-10-24T22:13:39Z",
        "registrar expiration": "2027-10-24T22:13:39Z",
        "last update of RDAP database": "2026-10-25T01:40:33Z"
    }
}
Separate source record · 14 malicious + 0 suspicious / 92 · 2026-10-25 21:22:16 UTC

The summary above and this provider record were collected at different times. Both remain available; malicious and suspicious classifications are shown separately.

record_source
collected_observations.vt
analysis_at
2026-10-25T21:22:16Z
fetched_at
2026-10-26T12:12:59Z
stats
{"timeout":0,"harmless":47,"malicious":14,"suspicious":0,"undetected":31}

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 11 fields

Observed: · Retrieved:

Report ID

345f2b03-b20b-4ee2-af53-fb73ff5c1075

Final URL

https://ticket-att.com/

Navigation history

  • URL
    https://ticket-att.com/
    Status
    0

DOM structure hash

222edc6576ce4f900a55dd02c5523f77c5fa64ee8b4e540f3ff8452026c169a8

URL risk categories

  • Phishing

Domain risk categories

  • Phishing
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    ticket-att.com
    Type
    A
    Value
    216.245.184.250

DNSSEC valid

No

Verdict

Tags
  • phishing
Malicious
Yes
Categories
  • phishing

Registration record

Registrar
Key-Systems GmbH
Registered
Updated
Expires
Nameservers
  • dns1.monsterdns.net
  • dns2.monsterdns.net
  • dns3.monsterdns.net
Original source fields · JSON
Uuid
345f2b03-b20b-4ee2-af53-fb73ff5c1075
Final url
https://ticket-att.com/
History
[
    {
        "url": "https://ticket-att.com/",
        "status": 0
    }
]
DOM structure hash
222edc6576ce4f900a55dd02c5523f77c5fa64ee8b4e540f3ff8452026c169a8
Url risks
[
    "Phishing"
]
Domain risks
[
    "Phishing",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "ticket-att.com",
        "type": "A",
        "value": "216.245.184.250"
    }
]
Dnssec valid
false
Verdict
{
    "tags": [
        "phishing"
    ],
    "malicious": true,
    "categories": [
        "phishing"
    ]
}
Registration record
{
    "registrar": "Key-Systems GmbH",
    "created": "2026-10-24T22:13:39Z",
    "updated": "2026-10-24T22:15:47Z",
    "expires": "2027-10-24T22:13:39Z",
    "nameservers": [
        "dns1.monsterdns.net",
        "dns2.monsterdns.net",
        "dns3.monsterdns.net"
    ]
}

URLScan

Malicious

Open report
URLScanOriginal source recordObserved: 22 fields

Observed: · Retrieved:

Report ID

01a1775e-ff77-7358-adb7-11c51951cf01

Final URL

https://www.ticket-att.com/wireless/step02.php

HTTP response

200

Redirect type

same-domain

Redirects

  • To
    https://www.ticket-att.com/wireless/step02.php
    From
    https://www.ticket-att.com/wireless/step01.php

IP address

216.245.184.250

Contacted IP addresses

  • 216.245.184.250

Autonomous systems (ASN)

  • 399629

Server countries

  • US

Linked domains

  • www.att.com

Document hash

b076acad8c5e456d1ac818fb95896ae0c20419873762f9a26994f85222604154

Script hashes

  • 3e7501d15c3630e791c8b20392eb9dee31a9f65ce3efdde76cef5c710141ab24
  • a106b0f8926e51c250f5055831c1673f12020d3fa1bfcfa4bb14f614dcd31a17

JavaScript globals

  • $
  • jQuery

Cookies

  • token

TLS session and certificate

Subject alternative names
  • ticket-att.com
  • www.ticket-att.com
Cipher
AES_128_GCM
Issuer
YE2
Subject
ticket-att.com
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

779

Registered domain age, days

2628

Certificate age, days

1

Certificate validity, days

89

Page requests

27

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
71
Malicious
Yes
Overall verdict
Tags
  • phishing
Score
100
Brands
  • att
Malicious
Yes
Categories
  • phishing
URLScan verdict
Tags
  • phishing
Score
100
Brands
  • AT&T
Malicious
Yes
Categories
  • phishing

HTTP headers

Server
Apache
Content-type
text/html; charset=UTF-8
Original source fields · JSON
Uuid
01a1775e-ff77-7358-adb7-11c51951cf01
Final url
https://www.ticket-att.com/wireless/step02.php
Status
200
Redirected
same-domain
Redirects
[
    {
        "to": "https://www.ticket-att.com/wireless/step02.php",
        "from": "https://www.ticket-att.com/wireless/step01.php"
    }
]
Ip
216.245.184.250
Contacted IP addresses
[
    "216.245.184.250"
]
Asns
[
    "399629"
]
Countries
[
    "US"
]
Linked domains
[
    "www.att.com"
]
Document hash
b076acad8c5e456d1ac818fb95896ae0c20419873762f9a26994f85222604154
Script hashes
[
    "3e7501d15c3630e791c8b20392eb9dee31a9f65ce3efdde76cef5c710141ab24",
    "a106b0f8926e51c250f5055831c1673f12020d3fa1bfcfa4bb14f614dcd31a17"
]
Globals
[
    "$",
    "jQuery"
]
Cookies
[
    "token"
]
Tls
{
    "san": [
        "ticket-att.com",
        "www.ticket-att.com"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE2",
    "subject": "ticket-att.com",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-22T21:21:44Z",
    "valid_from": "2026-10-24T21:21:45Z"
}
Domain age days
779
Apex age days
2628
Tls age days
1
Tls valid days
89
Requests
27
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 71,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "att"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "AT&T"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    }
}
HTTP headers
{
    "server": "Apache",
    "content-type": "text/html; charset=UTF-8"
}
Separate monitor record · date not recorded

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

record_source
domain_monitor.urlscan
uuid
01a1775e-ff77-7358-adb7-11c51951cf01
score
null
malicious
null
result_at
null
enriched_at
null
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":null}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

3 community references

Open report

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

100 / 100 · heuristic score · 0 brand references · 0 classifications

Open report
Separate monitor score · 0 / 100 · 2026-10-26T12:19:33Z

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

record_source
domain_monitor.dom_analysis
heuristic_score
0
analyzed_at
2026-10-26T12:19:33Z
source_timestamp
2026-10-26 13:19:33
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

ai_title
ticket-att.com — Suspicious Domain
ai_description
PhishDestroy flags ticket-att.com as a suspicious domain after fourteen VirusTotal detections and a malicious urlscan verdict linking it to the AT&T brand.
ai_generated_at
2026-10-26T12:16:01Z
ai_generated_by
threat-v3-groq
interpretation
Narrative generation metadata, separate from provider observation dates.

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

Collected source details

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

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 10 fields

Mail configuration

SPF lookups
0

CAA records

Domain
ticket-att.com

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Web archive observations

Last observation
First observation
Recorded changes
4
Archived days
5
Snapshots per day
0.02
Average page size, bytes
2609

DNS servers

Nameservers
  • IP address
    194.50.187.226
    Host
    ns2.rrpproxy.net
  • IP address
    194.0.182.226
    Host
    ns3.rrpproxy.net
  • IP address
    193.227.117.226
    Host
    ns1.rrpproxy.net
DNS zone
ticket-att.com

Location

IP address
216.245.184.250
ASN
399629
Organization
BL Networks
City
Chicago
Country
US

DNS records

A
  • 216.245.184.250
NS
  • ns1.rrpproxy.net
  • ns2.rrpproxy.net
  • ns3.rrpproxy.net
SOA
Primary nameserver
ns1.rrpproxy.net
Hostmaster
tech.rrpproxy.net
Serial
2026102402
Refresh, seconds
10800
Retry, seconds
3600
Expiry, seconds
604800
Minimum TTL, seconds
28800

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

IP lookup

IP address
216.245.184.250
IP version
4

Registration record

Registrar
Key-Systems GmbH
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • dns1.monsterdns.net
  • dns2.monsterdns.net
  • dns3.monsterdns.net
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "ticket-att.com"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2024-09-06T13:41:54Z",
    "first": "2023-12-28T21:50:46Z",
    "changes": 4,
    "days_archived": 5,
    "scans_per_day": 0.02,
    "avg_page_bytes": 2609
}
Dns server
{
    "ns": [
        {
            "ip": "194.50.187.226",
            "host": "ns2.rrpproxy.net"
        },
        {
            "ip": "194.0.182.226",
            "host": "ns3.rrpproxy.net"
        },
        {
            "ip": "193.227.117.226",
            "host": "ns1.rrpproxy.net"
        }
    ],
    "zone": "ticket-att.com"
}
Location
{
    "ip": "216.245.184.250",
    "asn": "399629",
    "org": "BL Networks",
    "city": "Chicago",
    "country": "US"
}
DNS records
{
    "A": [
        "216.245.184.250"
    ],
    "NS": [
        "ns1.rrpproxy.net",
        "ns2.rrpproxy.net",
        "ns3.rrpproxy.net"
    ],
    "SOA": "{\"nsname\": \"ns1.rrpproxy.net\", \"hostmaster\": \"tech.rrpproxy.net\", \"serial\": 2026102402, \"refresh\": 10800, \"retry\": 3600, \"expire\": 604800, \"minttl\": 28800}"
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Get ip
{
    "ip": "216.245.184.250",
    "family": 4
}
Registration record
{
    "registrar": "Key-Systems GmbH",
    "created": "2026-10-24T22:13:39Z",
    "updated": "2026-10-24T22:15:47Z",
    "expires": "2027-10-24T22:13:39Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "dns1.monsterdns.net",
        "dns2.monsterdns.net",
        "dns3.monsterdns.net"
    ]
}
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Phishing Security threats Phishing
View full Cloudflare Radar report

Questions about ticket-att.com

Is ticket-att.com legit?

No. PhishDestroy classifies ticket-att.com as a phishing page (risk: critical, 100/100); it was first detected on 2026-10-26. VirusTotal: 14/92 engines flag it. Treat the site as unsafe.

Is ticket-att.com safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on ticket-att.com. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used ticket-att.com?

Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.

Explore

Blocklist matchesOpenPhish · PhishDestroy · no match in the other 10 2
OpenPhish Listed View source
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 8 captures

Primary capture 1 / 8
SourcePrimary capture
Recorded
StateStored capture
HTTP status200
Final URLhttps://www.ticket-att.com/wireless/step02.php
Position1 / 8
Open capture Wayback Download
All capture links and hashes (8)
ticket-att.com: Phishing site — Flagged by OpenPhish, 14/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical).
Social preview card ticket-att.com: Phishing site — Flagged by OpenPhish, 14/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical). v 9ed674cf0b13

Domain details

Domain
IP Reputation abuse score 3/100 1 report Port ScanWeb App Attack checked Oct 26, 2026 last reported
OTX tags 2026-10all-domainsblocklistcryptodomainsdrainerfraudmonthlyphishdestroyphishingscam
Registrar Key-Systems DE(DE)
Abuse contact["abuse@key-systems.net", "a3fc02ecd75d3c23s@ticket-att.com.whoisproxy.org"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for ticket-att.com →
RegistrationExpires Oct 24, 2027
Registrant countryUnited States VirusTotal WHOIS
Registrant701706aef9b4109ca3fc02ecd75d3c23s@ticket-att.com.whoisproxy.org VirusTotal WHOIS
WHOIS statusclientTransferProhibited
Technical detailsProvenance & timestamps
First DetectedOct 26, 2026
DOM Analysisanalyzed Oct 26, 2026score 100/100
Submitted URLhttp://ticket-att.com/wireless/step01.php
Observed page title
ticket-att.com
TLS Certificate
Issued by Let's Encrypt / YE2 · stored validity ends in 88 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
216.245.184.250
Network ASN
AS399629
Organization
BL Networks
Observed location
Chicago, US
Server header
Apache

Nameservers 3

  • dns1.monsterdns.net
  • dns2.monsterdns.net
  • dns3.monsterdns.net

SOA

  • nsname: ns1.rrpproxy.net
  • hostmaster: tech.rrpproxy.net
  • serial: 2026102402
  • refresh: 10800
  • retry: 3600
  • expire: 604800
  • minttl: 28800

Registrar abuse contact VirusTotal WHOIS

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-10-24 21:21:45
Valid until
2027-01-22 21:21:44
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprinta6432c2b1838fd231e1269bd6ae456823c5c7c1534ebdccd7c33d3cab48a9342
Certificate names · 2 SANs
  • ticket-att.com
  • www.ticket-att.com

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

viewdns.info · 216.245.184.250rapiddns.io
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

14 / 92 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 14 detections
alphaMountain.ai
BitDefender
CRDF
Ermes
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Kaspersky
Lionic
MalwareURL
Netcraft
Sophos
Webroot
All retained availability observations1

Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.

  1. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 12:43:44.156225
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Monitoring · recorded

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

Pre-emptive Discovery & IngestionThreat Ingested Recorded: 1 of 1
  • Threat Ingested
    ticket-att.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Blocklist Detection · OTX Community References · Cloudflare Radar: Malicious · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 9 of 9
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan classified the page as malicious · Score: 100
  • Cloudflare Radar Report
    A stored Cloudflare Radar report is available. The report link alone does not mean that the domain was classified as malicious, and it does not prove that every network field was captured.
  • VirusTotal
    Detections recorded on VirusTotal: 14/92
  • Blocklist Detection
    Found in blocklists: OpenPhish
  • OTX Community References
    Community publication references on AlienVault OTX: 3. References are not vendor verdicts and are excluded from the evidence score.
  • Cloudflare Radar: Malicious
    Cloudflare Radar classified this domain as phishing, Security threats
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
Publication & AvailabilityDestroyList Published Recorded: 1 of 1

Recorded activity

5 entries
  1. AlienVault OTX

    3 community references

    View source
  2. VirusTotal

    14/92 engine detections

    View source
  3. Cloudflare Radar

    Phishing

    View source
  4. Added to PhishDestroy

    ticket-att.com

    View source
  5. URLScan

    Malicious

    View source
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

Check for cloaking

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

ticket-att.com

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 14 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid CF Radar Malicious OTX 3 refs 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 & reporting

Were You Affected by This Site?

4 evidence signal groups linked Unverified
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Silence is the scammer’s greatest advantage. Break it.
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.

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
More official reporting routes
FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect

Report to Your Local Authorities

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

Even if funds were frozen, they cannot be recovered without an official police report or court order. Submitting a complaint is the only path to potential recovery.

Scammers are criminals. Filing a report creates a legal record and helps protect others.

97-country directory

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

Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

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

What should I do immediately?

Urgent

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

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

What information should I collect for my report?

FBI guidelines

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.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including ticket-att.com)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?
  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

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?
  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?
  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

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

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

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 →
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.

Request a correction or appeal How PhishDestroy works
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/ticket-att.com"
  title="PhishDestroy threat report for ticket-att.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>