Hostname
agregate.info
Last fetched
agregate.info resolves to 104.21.77.219, announced in 104.21.64.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. agregate.info 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.77.219
104.21.64.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.211.234
172.67.208.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 190.2.145.38
190.2.144.0/20 · WorldStream - WorldStream B.V. · Naaldwijk, NL
- 172.239.194.103
172.239.192.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.239.193.153
172.239.192.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.236.108.16
172.236.96.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.237.129.108
172.237.128.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.237.129.242
172.237.128.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.237.129.236
172.237.128.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:1479
- Registrant organisation
- domains by proxy,
- Contact emails
- 0c83e5fff491295e_o@whoisprivacy.com, agregate.info@domainsbyproxy.com, pw-190ad8986c31340fc46675fc89e1e6ea@privacyguardian.org
Subdomains
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
- lovisa.ns.cloudflare.com
- mack.ns.cloudflare.com
- ns1.dnsowl.com
- ns2.dnsowl.com
- ns3.dnsowl.com
- ns1.parklogic.com
- ns2.parklogic.com
- ns1.ns306.parklogic.com
- ns2.ns306.parklogic.com
MX records
- mx156.hostedmxserver.com
- mail.eye-mail.net
Threat-feed evidence
History
Related pages
Pivot from agregate.info 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: "agregate.info"})-[: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.