Hostname
trifork.security
Last fetched
trifork.security resolves to 185.29.79.174, announced in 185.29.78.0/23 by NETIC-AS - Netic A/S in DK. trifork.security 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
IPv6 resolution
Attribution
netic
ORIGIN_AS
WHOIS identity
Subdomains
Showing 12 of 32. 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
Mail and authentication
Nameservers
- a.ns.netic.dk
- b.ns.netic.dk
- c.ns.netic.dk
MX records
- smtp.google.com
SPF policy
- ip: 77.243.50.192/26
- ip: 2a03:dc80:0:f136::/64
- include: _spf.google.com
- include: _spf.netic.dk
- include: 4087041.spf02.hubspotemail.net
- ip: 77.243.61.100
Threat-feed evidence
History
Related pages
Pivot from trifork.security 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: "trifork.security"})-[: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.