Skip to content

Hostname

tehy.fi

Last fetched

tehy.fi resolves to 104.20.42.252, announced in 104.20.32.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. tehy.fi is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · tehy.fiRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency6.7/10Resolver footprint8.0/10canon.whisper.security/host/tehy.fi

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrant organisation
tehy ry

Subdomains

Subdomain
adfs.tehy.fi
ao102.tehy.fi
ao104.tehy.fi
ao119.tehy.fi
ao121.tehy.fi
ao122.tehy.fi
ao125.tehy.fi
ao126.tehy.fi
ao128.tehy.fi
ao130.tehy.fi
ao131.tehy.fi
ao132.tehy.fi

Showing 12 of 249. 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.

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • brynne.ns.cloudflare.com
  • joaquin.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

  • tehy-fi.mail.protection.outlook.com

SPF policy

  • ip: 95.175.113.181/32
  • ip: 82.197.21.84/32
  • include: _spf.signicat.cloud
  • include: spf.lianamailer.com
  • include: spf.mailjet.com
  • include: spf.protection.outlook.com
  • include: mail.zendesk.com
  • include: mailgun.org
  • ip: 185.184.64.196
  • ip: 185.184.64.203
  • ip: 185.184.64.240
  • ip: 185.184.64.245

Threat-feed evidence

History

Related pages

Pivot from tehy.fi 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: "tehy.fi"})-[: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 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.