Hostname
umiperformance.com
Last fetched
umiperformance.com resolves to 172.66.40.129, announced in 172.66.40.0/21 by CLOUDFLARENET - Cloudflare, Inc. in CA. umiperformance.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
- 172.66.40.129
172.66.40.0/21 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.66.43.127
172.66.40.0/21 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:1068
- Registrant organisation
- lance kirkwood
- Contact emails
- lance@umiperformance.com, dd2f56e86cef4d839b5a6ab944e625a1.protect@whoisguard.com, ryan@umiperformance.com
Subdomains
| Subdomain |
|---|
| aap.umiperformance.com |
| chat.umiperformance.com |
| fb.umiperformance.com |
| media.umiperformance.com |
| review.umiperformance.com |
| test.umiperformance.com |
| umi-sales.umiperformance.com |
| www.umiperformance.com |
Showing 8 of 8 subdomains (8 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
- bill.ns.cloudflare.com
- zara.ns.cloudflare.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
- 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: _spf.google.com
- include: sendgrid.net
Threat-feed evidence
History
Related pages
Pivot from umiperformance.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: "umiperformance.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.