Hostname
performancehorizon.com
Last fetched
performancehorizon.com is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. performancehorizon.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
No IPv4 resolution is recorded for performancehorizon.com in WhisperGraph.
IPv6 resolution
No AAAA record for performancehorizon.com is recorded in WhisperGraph.
WHOIS identity
- Registrar
- iana:81
- Registrant organisation
- alex alanson
- Contact emails
- alex@easter-monday.com, 1880fe3ab30febca8280e9fc251b4154-1502124@contact.gandi.net, 85f2a7f012750957a64bad017dc0d192-1502124@contact.gandi.net, 8e25fd59eb020b97dbfe7b02e24e9e24-1502124@contact.gandi.net, 8e40f0b46f44887876b5af380f335e5e-6924644@contact.gandi.net, 944969ccefcaf404d39d5f0d6a01229e-1502124@contact.gandi.net, fafa22dc21d1b5ee6453439d5cc7b8f9-1502124@contact.gandi.net
Subdomains
Showing 12 of 71. View all 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
- edns1.ultradns.biz
- edns1.ultradns.com
- ns1.p24.dynect.net
- dns1.p01.nsone.net
- dns2.p01.nsone.net
- dns3.p01.nsone.net
- dns4.p01.nsone.net
- edns1.ultradns.net
- edns1.ultradns.org
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- aspmx2.googlemail.com
- aspmx3.googlemail.com
SPF policy
- include: amazonses.com
- include: cmail1.com
- include: _spf.google.com
- a: performancehorizon.com
- mx: performancehorizon.com
- include: mail.zendesk.com
- ip: 178.62.95.100
- ip: 5.150.168.10
- ip: 5.150.168.11
- ip: 5.150.168.19
- ip: 5.150.168.33
- ip: 5.150.172.21
Threat-feed evidence
History
Related pages
Pivot from performancehorizon.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: "performancehorizon.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.