Hostname
plazalecea.com
Last fetched
plazalecea.com resolves to 104.21.33.44, announced in 104.21.32.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. plazalecea.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 104.21.33.44
104.21.32.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 108.157.214.119
108.157.208.0/21 · AMAZON-02 - Amazon.com, Inc. · Stockholm, SE
- 108.157.214.21
108.157.208.0/21 · AMAZON-02 - Amazon.com, Inc. · Stockholm, SE
- 108.157.214.37
108.157.208.0/21 · AMAZON-02 - Amazon.com, Inc. · Stockholm, SE
- 108.157.214.96
108.157.208.0/21 · AMAZON-02 - Amazon.com, Inc. · Stockholm, SE
- 172.67.141.42
172.67.128.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 18.164.96.113
18.164.96.0/21 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 18.164.96.52
18.164.96.0/21 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 18.164.96.68
18.164.96.0/21 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 18.164.96.71
18.164.96.0/21 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:146
- Registrant organisation
- cecil yancey jr.
- Contact emails
- cyancey@ppdg.com
Subdomains
| Subdomain |
|---|
| www.plazalecea.com |
Showing 1 of 1 subdomain (1 per page).
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Mail and authentication
Nameservers
- ns-445.awsdns-55.com
- julian.ns.cloudflare.com
- meadow.ns.cloudflare.com
- ns-775.awsdns-32.net
- ns-1470.awsdns-55.org
- ns-1627.awsdns-11.co.uk
MX records
- arrow.mxrouting.net
- arrow-relay.mxrouting.net
SPF policy
- include: mxlogin.com
Threat-feed evidence
History
Related pages
Pivot from plazalecea.com into the addresses, networks and registries it depends on.
Cypher and MCP
Reproduce this hostname's resolution chain against graph.whisper.security:
MATCH (h:HOSTNAME {name: "plazalecea.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.