Hostname
cynergy3.com
Last fetched
cynergy3.com resolves to 104.18.4.206, announced in 104.18.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. cynergy3.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.18.4.206
104.18.0.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 104.18.5.206
104.18.0.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
No AAAA record for cynergy3.com is recorded in WhisperGraph.
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:292
- Registrant organisation
- cynergy3 components
- Contact emails
- abuse@web.com, br3jm73t5na@networksolutionsprivateregistration.com, fmaytorena@crydom.com, pnorris@cynergy3.com
Subdomains
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Sample inbound links
Mail and authentication
Nameservers
- ns1.markmonitor.com
- ns2.markmonitor.com
- ns3.markmonitor.com
- ns4.markmonitor.com
- ns5.markmonitor.com
- ns6.markmonitor.com
- ns7.markmonitor.com
- a.root-servers.net
- b.root-servers.net
- c.root-servers.net
- d.root-servers.net
- e.root-servers.net
- f.root-servers.net
- g.root-servers.net
- h.root-servers.net
- i.root-servers.net
- j.root-servers.net
- k.root-servers.net
- l.root-servers.net
- m.root-servers.net
MX records
- mxa-0024ff01.gslb.pphosted.com
- mxb-0024ff01.gslb.pphosted.com
SPF policy
- a: cynergy3.com
- mx: cynergy3.com
- a: mxa-0024ff01.gslb.pphosted.com
- a: mxb-0024ff01.gslb.pphosted.com
- include: c3internal.email
- include: impress-internal.email
- ip: 51.148.114.92
Threat-feed evidence
History
Related pages
Pivot from cynergy3.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: "cynergy3.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.